OK, I never got this "object" stuff, it's kinda confusing because it
tends to make much ado about nothing (in poor implementations, yes,
but I've only seen poor ones, the Newton being very hard to understand
in terms of how to use). As for VMS file attribs does anyone know how
many there actually were? I counted the attribs Norton DiskEdit lets
me change on the Mac (bundle, locked, bozo, init, etc.), and there
are at least 30.
DOS in terms
of having an array of blocks and stuff. Except Apple's
is quite a bit more elegant. Since some people here are fond of
praising the VAX, how does its file system work (typically)?
The Newton "soup" is an object store rather than a directory hierarchy,
and you'll probably see that paradigm more often in the future. I
think
Microsoft's "Cairo" road-map included
turning the filesystem into an
object store.
"VAX" is a hardware architecture. Lots of people run Unix on VAXen.
But the VAX-philopsophy was extreme CISC, and that extended to the
VAX/VMS
filesystem as well: record-based, with a zillion
different file
attributes, built-in file versioning, etc. It was hierarchial, but
mixed
with a clunky "volume" concept (something
like DOS "C:", but with
longer
names).
-- Doug
______________________________________________________
Get Your Private, Free Email at
http://www.hotmail.com