[ruby-core:28514] Re: [Feature #2759] Regexp /g and /G options

On 3/4/10, NARUSE, Yui <[e-mail]> wrote:
> 2010/3/5 Caleb Clausen <[e-mail]>:
>> Can't you rewrite that as something like this:
>>
[code snipped]
>>
>> That is, use the old format if the regexp options will fit in a byte,
>> else use a new format with a wider field for options. There'd be
>> similar logic on the unmarshal side. This new regexp format would be
>> unreadable on older ruby versions, but then they won't know what to do
>> with 256 in the options field anyway, so there's no loss there.
>
> This code allows 1.9.2 to dump and load older regexps and new extended
> regexps.
> But when older than Ruby 1.9.2 can't load all of dumped data
> which include such dumped wideregexp,

Yes, but that doesn't matter, because a ruby from before this new
regexp option was added will never be able to do the right thing with
a regexp that has this newly invented option, even if it could somehow
be deserialized without error.

> I'm thinking the way to dump the regexp as normal object and invisible
> instance
> encoding.

Not being conversant with marshal's internals myself, I have no idea
what this means.... :)
I'll just assume that your idea, whatever it is, is better.