Kyle Furlong wrote:
> Perhaps once PyD is rock solid, Kirk could take a crack at RuD? (Rudy?) (RubyD?) The problem is roughly equivalent, allowing for eccentricities in their respective C API's.

I've looked at doing this, actually. Two things stand in my way, both surmountable:

(1) I don't know Ruby or, by extension, the Ruby C API very well. The documentation for it isn't very good either. (Of course, the same could be said about parts of the Python/C API.) I am simply not as into Ruby as I am into Python.

(2) There are no complete D bindings for the Ruby API, and I don't really have the patience to write them. Though much of the API can be automatically bound with htod or BCD (and I have an htod version around here somewhere), portions of it consist of macros or macro functions that can't be automatically converted. Deja Augustine and David Rushby had already written the Python/C bindings before I ever started Pyd, and my interest in writing a "Rudy"-type project would be greatly improved if I didn't have to do the drudge work of writing the bindings.

-- 
Kirk McDonald
Pyd: Wrapping Python with D
http://pyd.dsource.org

On Tue, 2 Jan 2007, Walter Bright wrote:

> I know you all are early adopters of D, and that's a special breed different from the vast majority of programmers. But still, it would be useful (in writing documentation) to know what language was your primary tool before coming to D. I also know that many of you are handy with multiple diverse languages, I just want to know the primary one.
> 
> Asm?
> C++?
> C?
> None (D's your first language)?
> Java?
> C#?
> Python?
> Lisp?
> Ruby?
> Delphi?
> Perl?
> Cobol? <g>

c (and really C, not just a standard pat answer of c/c++), c++ primarily

perl, bash secondarily

java a tad

pascal, asm, fortran (missing from your list) in professional capacities at one point or another though none in the last 10 years.

Later,
Brad

c++

Walter Bright wrote:
> I know you all are early adopters of D, and that's a special breed different from the vast majority of programmers. But still, it would be  useful (in writing documentation) to know what language was your primary tool before coming to D. I also know that many of you are handy with multiple diverse languages, I just want to know the primary one.

I'm a bottoms up guy:

ASM (various + microcode), C, C++, Python

D is not there yet, only for fast testers at the moment.

Na zdrowie!

Kirk McDonald wrote:
> Kyle Furlong wrote:
>> Perhaps once PyD is rock solid, Kirk could take a crack at RuD? (Rudy?) (RubyD?) The problem is roughly equivalent, allowing for eccentricities in their respective C API's.
> 
> I've looked at doing this, actually. Two things stand in my way, both surmountable:
> 
> (1) I don't know Ruby or, by extension, the Ruby C API very well. The documentation for it isn't very good either. (Of course, the same could be said about parts of the Python/C API.) I am simply not as into Ruby as I am into Python.
> 
> (2) There are no complete D bindings for the Ruby API, and I don't really have the patience to write them. Though much of the API can be automatically bound with htod or BCD (and I have an htod version around here somewhere), portions of it consist of macros or macro functions that can't be automatically converted. Deja Augustine and David Rushby had already written the Python/C bindings before I ever started Pyd, and my interest in writing a "Rudy"-type project would be greatly improved if I didn't have to do the drudge work of writing the bindings.
> 

Actually I think "Rudy" is a cute name for it.  Although it might lead to "Rudolph" jokes... so be it.  We'll just make its mascot a reindeer and be done with it.

In all seriousness, perhaps a project could be started to this end?  I'm sure there would be others (myself included) willing to donate a little time to writing bindings and working out how best to hook it up.  Then with your experience from working on PyD, and general Ruby users' enthusiasm, we might just cook up something tasty.  :)

-- Chris Nicholson-Sauls

Chris Nicholson-Sauls wrote:
> Actually I think "Rudy" is a cute name for it.  Although it might lead to "Rudolph" jokes... so be it.  We'll just make its mascot a reindeer and be done with it.

"Rudy" is perfect.

Coming from C++. I don't really know any other language well.
Before C++, I used a program called Multimedia Fusion. While it doesn't use a
typed language, in a way it still is programming.

Walter Bright wrote:
> Chris Nicholson-Sauls wrote:
>> Actually I think "Rudy" is a cute name for it.  Although it might lead to "Rudolph" jokes... so be it.  We'll just make its mascot a reindeer and be done with it.
> 
> "Rudy" is perfect.

"Rubidium" was another one that comes to mind.

Walter Bright wrote:
> I know you all are early adopters of D, and that's a special breed different from the vast majority of programmers. But still, it would be  useful (in writing documentation) to know what language was your primary tool before coming to D. I also know that many of you are handy with multiple diverse languages, I just want to know the primary one.
> 
> Asm?
> C++?
> C?
> None (D's your first language)?
> Java?
> C#?
> Python?
> Lisp?
> Ruby?
> Delphi?
> Perl?
> Cobol? <g>

C++.

bls wrote:
> Fortran rules, allways good to see a language without having any features
> (difficult things like recursion. ..Allways good to keep this stuff away
> from math !)
> is able to survive.    Men I mean we are not working on a PDP11  anymore!
> 
> At least some hope for D     <vvbg>  .
> Bjoern

I used to do Fortran on an 11!

Let's see. I started with BASIC on something called a "Business 6" computer, perhaps I got the name wrong. Programmed it with punch card decks. Wish I'd kept one of my old card decks!

Upgraded to Basic on a PDP-10. Rapidly outgrew that, went on to FORTRAN-10, MACRO-10, then 6800 asm, 6502 asm, that crazy 10 bit byte CPU I forgot the name of in the Mattel Intellivision, Pascal, FORTRAN-11, MACRO-11, swore off computers, 8088 asm, C, C++, Java, Javascript, D.

Notably absent is Lisp. I did some emacs lisp programming, but never liked it and never got the hang of it.