[EMAIL PROTECTED] wrote:
> Hi Gabriele,
> you wrote:
> >People complaining about not being able to do lowlevel I/O, should
> >really be complaining about their OS being too limited.
>
> On the same note I've been thinking of formalizing a Standard REBOL
> Execution Environment (SREE ;-), which would specify OS extensions that
> would allow a seamless integration of REBOL. I.e. Open the OS's API for
> REBOL port access and provide an interface specification that ensures that
> REBOL scripts will be able to use stand interface words to access OS
> specific capabilities.
>
> Basically, there would be a gateway process available on a local or remote
> machine, which is accessable via a standard port and supports the SREE
> standard interface specification. If I want to read/write to serial port,
> for instance, I access the specified port and use user supplied, platform
> specific implementations of standardized words, to communicate with the
> REBOL - OS Gateway on the target machine. The words are universal, their
> implementation is system specific. On a different platform, my script calls
> the same words, they interact with the gateway process in a way that is
> compatible with that platform.
>
> 1. I'm not sure to what degree that is possible.
> 2. Since extended versions of REBOL have been announced, this kind of
> effort may become obsolete very soon and therefore I'm not motivated to
> pursue this idea too far.
>
> Any thoughts?
1) Let's wait, what App-Talk, feature mentioned on REBOL website is going to
provide us ...
2) Jeff, in one of his last replies mentioned:
However:
Though there won't be support in REBOL/core to talk to
peripherals, this doesn't mean that other REBOL
products won't have this capability, or allow you to
essentially ADD this feature to them in a simple
REBOLian way. Can't say much more-- but hopefully this
info will console those of you who are wishing for that
capability. :-)
Whatever above means :-)
-pekr-
>
>
> Elan
