# Ruby Design Meeting 4/30

**URL:** <https://www.ruby-forum.com/t/ruby-design-meeting-4-30/136384>\
**Category:** IronRuby\
**Created:** [May 1, 2008, 3:01pm UTC](https://www.ruby-forum.com/t/ruby-design-meeting-4-30/136384 "2008-05-01T15:01:28Z")\
**Posts on this page:** 3\
**Page:** 1

<div class="post-metadata">

**Author:** ![dreamwave](https://www.ruby-forum.com/letter_avatar_proxy/v4/letter/d/7feea3/32.png) [@dreamwave](https://www.ruby-forum.com/u/dreamwave)\
**Post date:** [May 1, 2008, 3:01pm UTC](https://www.ruby-forum.com/t/ruby-design-meeting-4-30/136384/1 "2008-05-01T15:01:28Z")

</div>

I attended the Ruby Design  
[http://ruby-design.pbwiki.com/Design20080430](http://ruby-design.pbwiki.com/Design20080430)meeting for last night.  
Since it appears that I was the only person working  
on IronRuby in any fashion there, I thought I’d share some of the  
results of  
the meeting with everyone. First of all, let me say the meeting was  
quite  
educational, it’s not often you get to sit and listen to a bunch of  
really  
smart people discuss the ins and outs of language design. It was quite  
orderly and the feeling of collaboration was almost tangible. While a  
number  
of items have to be worked out over time, at least the meeting gets all  
the  
different implementors thinking about certain topics.

The most important topic that’s immediately relevant is probably the  
decision that all implmentations will use RUBY\_ENGINE to report which  
implementation they are, in all lowercase with no spaces. It seems  
pretty  
obvious that IronRuby would be “ironruby”. Attached is a patch  
implementing  
that. Most of the other topics are things we’re not implementing yet,  
but  
things that should be considered. Feel free to look over the transcript:  
[http://ruby-design.pbwiki.com/f/ruby-core-20080430.txt](http://ruby-design.pbwiki.com/f/ruby-core-20080430.txt) for details.  
Most  
of the other topics are going to spawn threads in the main ruby-core  
list  
anyway.

The next meeting is set for 5/15, hope to see some of you there!

---

<div class="post-metadata">

**Author:** ![dreamwave](https://www.ruby-forum.com/letter_avatar_proxy/v4/letter/d/7feea3/32.png) [@dreamwave](https://www.ruby-forum.com/u/dreamwave)\
**Post date:** [May 1, 2008, 3:21pm UTC](https://www.ruby-forum.com/t/ruby-design-meeting-4-30/136384/2 "2008-05-01T15:21:28Z")

</div>

Michael L.:

> The most important topic that’s immediately relevant is probably the  
> decision that all implmentations will use RUBY\_ENGINE to report which  
> implementation they are, in all lowercase with no spaces. It seems  
> pretty obvious that IronRuby would be “ironruby”. Attached is a patch  
> implementing that.

Unfortunately, that time works out horribly for me since that’s when I  
put the boys to bed. Thanks for sending around the notes - I’ve already  
applied your patch to my local copy here.

Thanks,  
-John

---

<div class="post-metadata">

**Author:** ![dreamwave](https://www.ruby-forum.com/letter_avatar_proxy/v4/letter/d/7feea3/32.png) [@dreamwave](https://www.ruby-forum.com/u/dreamwave)\
**Post date:** [May 1, 2008, 6:41pm UTC](https://www.ruby-forum.com/t/ruby-design-meeting-4-30/136384/3 "2008-05-01T18:41:41Z")

</div>

John L. (IRONRUBY) wrote:

> Michael L.:
> 
> > The most important topic that’s immediately relevant is probably the  
> > decision that all implmentations will use RUBY\_ENGINE to report which  
> > implementation they are, in all lowercase with no spaces. It seems  
> > pretty obvious that IronRuby would be “ironruby”. Attached is a patch  
> > implementing that.
> 
> Unfortunately, that time works out horribly for me since that’s when I put the boys to bed. Thanks for sending around the notes - I’ve already applied your patch to my local copy here.

John, you should definitely bring this up on the list. Nobody replied to  
Matz’s last message about the second meeting, so we went forward. The  
next meeting is scheduled for the 15th/16th at the same time of day. If  
the time doesn’t work, it can be adjusted. But you need to let ruby-core  
know…we miss you!

- Charlie
