Is the Ruby executable written in C?

ruby-talk
1

Hi all,

Is the Ruby executable written in C?

Thanks

SteveT

Steve Litt
http://www.troubleshooters.com
slitt@troubleshooters.com

2

In a word: Yes.

James Edward Gray II

···

On Dec 30, 2005, at 9:39 AM, Steve Litt wrote:

Hi all,

Is the Ruby executable written in C?

3

Steve Litt wrote:

Is the Ruby executable written in C?

It seems to be written in a version of C that I found a little difficult to read. It uses old K&R style function declarations, and uses macros in places I'm not used to seeing them. Honestly, I'd love to spend some time hacking the VM, but it looks prohibitively difficult. Maybe someone will enlighten me. :slight_smile:

4

Steve Litt wrote:

Hi all,

Is the Ruby executable written in C?

yes.

5

modulo JRuby

···

At 12:50 AM +0900 12/31/05, James Edward Gray II wrote:

On Dec 30, 2005, at 9:39 AM, Steve Litt wrote:

Hi all,

Is the Ruby executable written in C?

In a word: Yes.

--
email: rdm@cfcl.com; phone: +1 650-873-7841
http://www.cfcl.com - Canta Forda Computer Laboratory
http://www.cfcl.com/Meta - The FreeBSD Browser, Meta Project, etc.

6

Jeffrey Schwab <jeff@schwabcenter.com> writes:

Steve Litt wrote:

Is the Ruby executable written in C?

It seems to be written in a version of C that I found a little
difficult to read. It uses old K&R style function declarations, and
uses macros in places I'm not used to seeing them. Honestly, I'd love
to spend some time hacking the VM, but it looks prohibitively
difficult. Maybe someone will enlighten me. :slight_smile:

The Perl source is worse.

*scnr*,

···

--
Christian Neukirchen <chneukirchen@gmail.com> http://chneukirchen.org

7

Jeffrey Schwab wrote:

Steve Litt wrote:

Is the Ruby executable written in C?

It seems to be written in a version of C that I found a little difficult to read. It uses old K&R style function declarations, and uses macros in places I'm not used to seeing them. Honestly, I'd love to spend some time hacking the VM, but it looks prohibitively difficult. Maybe someone will enlighten me. :slight_smile:

Might be an acquired taste. I've not done any regular C coding in many years, (which may have helped here) but when crawling through the Ruby source some years back, in preparation for a book, I found it fairly easy to get used to the naming and coding conventions and figure things out. It was a great help when trying to determine if some class or method had any potentially unexpected behavior that was not documented, or not documented correctly.

(I realize it may seem pretty obvious to say that the source code is a good place to look for this information, the point being that it is quite readable.)

James

···

--

http://www.ruby-doc.org - Ruby Help & Documentation
Ruby Code & Style - Ruby Code & Style: Writers wanted
http://www.rubystuff.com - The Ruby Store for Ruby Stuff
http://www.jamesbritt.com - Playing with Better Toys
http://www.30secondrule.com - Building Better Tools

8

According to Nat Torkington, the Perl source is "an interconnected mass
of livers and pancreas and lungs and little sharp pointy things and the
occasional exploding kidney."

···

On Sat, Dec 31, 2005 at 10:34:19PM +0900, Christian Neukirchen wrote:

Jeffrey Schwab <jeff@schwabcenter.com> writes:

> Steve Litt wrote:
>
>> Is the Ruby executable written in C?
>
> It seems to be written in a version of C that I found a little
> difficult to read. It uses old K&R style function declarations, and
> uses macros in places I'm not used to seeing them. Honestly, I'd love
> to spend some time hacking the VM, but it looks prohibitively
> difficult. Maybe someone will enlighten me. :slight_smile:

The Perl source is worse.

--
Chad Perrin [ CCD CopyWrite | http://ccd.apotheon.org ]

"A script is what you give the actors. A program
is what you give the audience." - Larry Wall