I've been looking at what it would take to start using byte arrays rather
then strings for the backing store for MutableString. It's one heck of a
rabbit hole, I can get it /almost/ working... either I fail one spec, or
three... and they're totally different. Anyway, if noone else is working on
it I'll continue to see what I can do, this is related to the zlib issue
with binary files (or actually any file that contains bytes over 127
potentially) as data is passed around as strings and not byte arrays.
Oh and I hope to implement actual compression sometime soon.. just need to
block out some time.
On Fri, May 2, 2008 at 6:24 PM, John Lam (IRONRUBY) <[EMAIL PROTECTED]>
wrote:
> I'm still working on the shelveset that I sent out for code review earlier
> today (bugfixes9). We found a few more issues when we did the code review.
> The most interesting case is this one:
>
> We normally define methods that accept symbol using a signature that takes
> a SymbolId, eg:
>
>
> [RubyMethod("attr", RubyMethodAttributes.PrivateInstance)]
> public static void Attr(CodeContext/*!*/ context, RubyModule/*!*/ self,
> SymbolId name) {
> DefineAccessor(context, self, name, true, false);
> }
>
>
> Methods like these will blow up if you pass it a 'string-like' thing. We
> have a Protocol to convert these things - Protocols.CastToSymbol(), which
> does the right thing, which is call to_str on the target.
>
> We have an open question right now which is whether we should bake in
> object to SymbolId conversions in the binder or whether we should handle
> them in a case by case basis by defining an overload that accepts an Object,
> and calling Protocols.CastToSymbol() on that object.
>
> Once I get this shelveset past the troll, I'll work next on getting
> socket.cs and the ironi regex library into the tree.
>
> Thanks,
> -John
>
> From: [EMAIL PROTECTED] [mailto:
> [EMAIL PROTECTED] On Behalf Of Jim Deville
> Sent: Friday, May 02, 2008 2:37 PM
> To: [email protected]
> Subject: [Ironruby-core] Friday Status Update
>
> Like we talked about earlier, let's give an update on what we are working
> on
>
> I'm working on hacking optparse to work so that we can update to the
> newest Rubinius spec's. Then I'll be closing out a whole slew of bugs.
>
> Jim Deville
> _______________________________________________
> Ironruby-core mailing list
> [email protected]
> http://rubyforge.org/mailman/listinfo/ironruby-core
>
--
Michael Letterle
[Polymath Prokrammer]
http://blog.prokrams.com
_______________________________________________
Ironruby-core mailing list
[email protected]
http://rubyforge.org/mailman/listinfo/ironruby-core
