On May 26, 2010, at 6:08 PM, Charles Oliver Nutter wrote: > There's bound to be at > least one path that receives RubyFloat that we can't full inline, and > that one path would mean the object needs to exist...right?
Yes. That's why it's fragile. -- John -- You received this message because you are subscribed to the Google Groups "JVM Languages" group. To post to this group, send email to jvm-langua...@googlegroups.com. To unsubscribe from this group, send email to jvm-languages+unsubscr...@googlegroups.com. For more options, visit this group at http://groups.google.com/group/jvm-languages?hl=en.
