+1
On Dec 26, 3:41 am, Kevin Clark kevin.cl...@gmail.com wrote:
Maybe a '-O' makes sense in general for optimizations that are going
to make debugging ugly?
--
Kevin Clarkhttp://glu.ttono.us
--
--- !ruby/object:MailingList
name: rubinius-dev
view:
Maybe a '-O' makes sense in general for optimizations that are going
to make debugging ugly?
--
Kevin Clark
http://glu.ttono.us
--
--- !ruby/object:MailingList
name: rubinius-dev
view: http://groups.google.com/group/rubinius-dev?hl=en
post: rubinius-dev@googlegroups.com
unsubscribe:
Hi Simon,
On Dec 24, 2:19 am, Simon Harris haruki.zae...@gmail.com wrote:
Does rubinius perform any kind of TOC or are there any plans?
We currently do not do any tail call optimizations. One big reason is
that tail call optimizations typically destroy proper backtrace
information. I consider
I understand the rationale but explicit TOC is, IMHO, nasty. How about
a VM-wide switch instead? Then I've made it explicit that I accept the
consequences of the optimisation. I can then develop on the small
without TOC and execute on the large with it. It also means the code
is technically
