From: stephan b. <st...@s1...> - 2004-12-25 23:24:48
|
Yo! Marc and i just had a long IRC discussion, and i can't believe i never thought of this earlier: The s11n core itself is some 50 lines of code, so it will be trivial to plug it in directly to the P tree. i'll need to port in supporting algos and types, but i will not bring in the i/o layer (the biggest part, by far). i can swap out the factory layer with little work, as well. This will allow us to put serialization in place anywhere in P (where it's practical/useful), without an external dep on s11n. We can worry about the i/o layer later, either linking against s11n's, providing our own porting in s11n's i/o layer (which would need some serious rework, i think, to remove a lot of deps),or whatever. The important part of serialization is the core container framework - the actual stream i/o is a bonus. The new module will be P::S11n, of course. Unfortunately, the naming conventions in the s11n code won't all be easily sed'able to P naming conventions (try "grep s11n *" ;), and that will take some time to fix, but otherwise the port should be pretty straightforward. An interesting thing about this is: by leaving out the i/o layer, we immediately lose the only platform-dependent part which s11n has! That means P::S11n will be inherently portable to all P-support platforms. :) -- ----- st...@s1... http://s11n.net "...pleasure is a grace and is not obedient to the commands of the will." -- Alan W. Watts |