Re: Opencomm: proplib-based syscall

[der Mouse <mouse%Rodents-Montreal.ORG@localhost>]

> In fact, fundamentally it is completely the same thing as the current
> model [for mount(2)].  You can just as well pass uint8_t[] read from
> a file and have the same problems and same responsibilities.

> Say the argument is
[compressed vertically -dM]
> struct { a; b; }

> And the relevant xml is <a></a><b></b>.  What needs to happen if you
> need to add "c", change "a" or remove "b"?

Things that do _not_ happen: adding a "c" starts using uninitialized
memory after the struct; changing "b" to "c" starts using old-userland
"b" values as if they were "c" values.

Yes, some cases will return errors.  But they'll return sensible
errors, not random errors that make no sense unless you look at how
bits are getting reinterpreted (or, worse, non-errors because the
reinterpreted bits made enough sense to be used).

Not that I like proplib (and XML more generally); I don't.  But this
actually is one case where it gets things righter than the old way.

/~\ The ASCII                             Mouse
\ / Ribbon Campaign
 X  Against HTML                mouse%rodents-montreal.org@localhost
/ \ Email!           7D C8 61 52 5D E7 2D 39  4E F1 31 3E E8 B3 27 4B