At 11:29 PM -0700 8/18/02, Brian Ingerson wrote:
>On 18/08/02 16:06 -0400, Dan Sugalski wrote:
>> Okay, here's two new vtable methods
>>
>> freeze(PMC) - Responsible for freezing a PMC to the current freeze
>> data stream. Throws an exception on error
>>
>> thaw(PMC) - A class method that thaws a PMC from the current
>>thaw data stream
>>
>> Both of these should use the freeze/thaw API--I'll get that defined
>> and out shortly.
>
>If I want to provide YAML serialization support at the Parrot level, would I
>be able to simply override these methods?
Nope. What you do instead is override the
serialization/deserialization code that abstracts the
freezing/thawing, which the PMCs use to serialize/deserialize
themselves. :)
I don't particularly want to specify a single blessed way of encoding
the data, as I'm not sure what the best way to do it is. The only
thing I think we will mandate is that the first bit of the data file
reads something like:
<ENCODING type="parrot" version=x.x>\n
(only XML-y) just so we have a fixed string to parse out to make sure
we can figure out how to process the data. I'd be OK adding an
encoding in there too.
The one thing I *don't* want is a proliferation of different
encodings--then either we get interoperability problems with installs
that lack a decoder, or we build in a zillion different ways to do
the same damn thing, and that seems rather a waste.
--
Dan
--------------------------------------"it's like this"-------------------
Dan Sugalski even samurai
[EMAIL PROTECTED] have teddy bears and even
teddy bears get drunk
