🚀 go-pugleaf

In article <12940@cbmvax.commodore.com>, peter@cbmvax.commodore.com (Peter Cherna) writes:
>
> > I initially asked:
> > Anyone know what the implementation of environment variables will be in
> > the final version of 2.0?  Still the 1.3 "files" implementation, or will
> > env: be a real device as it was to become "eventually"?
>
> How things are implemented is less of a concern than how they work.  There
> is more than one place in the system where we could change the implementation
> because the function interface is well defined.

That may be true in theory Peter, but I am working on some code *now* that
requires an env var or two.  And since I currently have to roll my own fn()
(since it was not provided by CBM in 1.3), I would like to know whether I'll
need to change it under 2.0.  Eventually (read: when the 2.0 Native Developer
Package, or whatever is available), I'll change the code to use the official
library call, assuming there is one in this release, but it'd be nice to know
ahead of time if there will be problems due to a change in the implementation.

So I ask again, will the 2.0 implementation be of the "files" variety, or will
env: be a real device (as your "BTW" below would seem to imply)?


> BTW, another big difference is your application can be automatically
> notified when an environment variable changes.

Sounds like a very useful enhancement.  How's this accomplished?

Thanks ...!

/kim

-- 
UUCP:  kim@uts.amdahl.com
  or:  {sun,decwrl,hplabs,pyramid,uunet,oliveb,ames}!amdahl!kim
DDD:   408-746-8462
USPS:  Amdahl Corp.  M/S 249,  1250 E. Arques Av,  Sunnyvale, CA 94086
BIX:   kdevaughn     GEnie:   K.DEVAUGHN     CIS:   76535,25