Eckard Brauer wrote:
But how about having something like init(url:...), init(name:...), or
init(stream:...), where the ellipsis after stream: could be stdin,
stdout or stderr?
For me, even having only init(name:<ressource>) would make sense, when
thinking of <ressource> as e.g.:
"http://..."; - have some HTTP ressource,
"file://..." - have some filesystem (accessible) ressource,
or even:
"webdav://..." - WebDAV ressources may be writable, but will have to be
retrieved from remote site first,
"mailto://..."; - send stream per mail,
and of course:
"stdin:", "stdout:", and "stderr:" - for the standard streams, and
"pipe:..." for reading from or writing to a command.
This mechanism in turn would need to have some basic or widely used
protocol types (file, http, ftp, ...) implemented and a way to
implement new protocol types.
Or (where, if so?) does this conflict with some idea of what Mozart/Oz
is thought to be?
Eckard
This is all possible. The basic principle of Mozart/Oz design is to
keep all the concepts factorized, so they can be combined in all
possible ways that make sense. This could be done here too.
Peter
_________________________________________________________________________________
mozart-users mailing list
[email protected]
http://www.mozart-oz.org/mailman/listinfo/mozart-users
