ron minnich wrote:
This one is interesting:
"The acmpolicy class implements a compiler for translating an XML policy
into their binary format and provides functionality for comparing a
current policy against a new one when changing a policy."
So, translate XML to binary to use it?
But it's a standard, right? I can't tell you how many times a day
people tell me they're doing something in XML ... "it's the standard"
-- not "A", but "THE".
Let's see:
<9p><request>T</request><requesttype>R</requesttype><fid><number><digit><binary>1</binary><binary>0>/binary>...
well, you get my drift.
Shouldn't we move 9p to a standards-based, compliant, XML-based system
with first-class enumerated elements in which all pluggable components
are Python objects and hence first-class citizens and add a full
compiler to enable translation and XML co-processor acceleration?
Can I randomly permute the words in the previous sentence? Yes.
Is that sentence like stuff I read nowadays? Yes.
Is constant gnashing wearing off the enamel on my teeth? Yes, oh yes.
ron
Not to worry!
Sign of the times.
'Standards based' has simply replaced 'they say' as the biggest liar in the
world.
Going the other way, we can now shave 3 bytes:
'progress' can be expressed as 'bloat'
Bill
