[pclasses-devel] Re: s11n core coming to P :)

[stephan b. <st...@s1...>]

On Sunday 26 December 2004 00:23, stephan beal wrote:
> The s11n core itself is some 50 lines of code, so it will be trivial
> to plug it in directly to the P tree. 

You're not going to believe this, but... i'm done. Well, i mean:

a) i've pulled in the absolute minimum needed to build the core 
interface and all of the various algos/proxies. (The core is tiny, but 
without algos it's useless.)

b) it compiles under the P tree, after changing some of the code to use 
P types, like the Factory and LexT.

It still needs to be tested and some minor changes made, of course.

Caveats:

a) Porting the entire code to the P naming conventions won't be 
practical, i think. The main problem is that the word 's11n' shows up 
*everywhere* in this tree.

b) i have kept the module name 's11n', not 'S11n', because changing it 
would probably require that i do (a). i will move it into the P::s11n 
namespace, but it's currently under ::s11n.

c) there is no i/o layer, which means no file formats whatsoever are 
supported at this point. We can, however, build complete de/ser support 
without any file i/o, as de/ser is, from the client's perspective, 
container-based.

d) there are currently several util namespaces which should go away.

But it builds.

If the general naming conventions are a problem let me know and i will 
attempt to sed the classes. 

One advantage to allowing the P::s11n namespace to follow s11n's 
existing naming conventions is that i can freely swap code between the 
two projects and be confident that renamings didn't break anything. i 
agree that it would be nicer to rename the types, though.



-- 
----- st...@s1...   http://s11n.net
"...pleasure is a grace and is not obedient to the commands
of the will." -- Alan W. Watts