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.
<snip>

C++ for some purposes, Java for others.

Stewart.

C/C++, Java and C#.

C/C++ is the one I'm wanting to be replaced by D.


-- 
Bruno Medeiros - MSc in CS/E student
http://www.prowiki.org/wiki4d/wiki.cgi?BrunoMedeiros#D

Kyle Furlong wrote:
> Jeff M wrote:
>> On 2007-01-02 15:29:03 -0800, Walter Bright <newshound@digitalmars.com> said:
>>
>>> 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>
>>
>> My primary language is PHP, but I have a good knowledge of the following languages:
>>
>> * PHP (including PHP Internals)
>> * C
>> * C++
>> * C#
>> * ECMAScript
>> * SQL
>>
>> At one time I knew these languages:
>>
>> * Perl
>> * Java
>>
>> I've been learning D for the past two weeks.  It's like C++ except that it doesn't make me want to shove knitting needles into my eyes.
>>
>> -- Jeff
>>
> 
> I love these newcomer anecdotes. :D

When commenting about C++ to coder friends I usually describe it as making me "want to dig inside my skull and scrape out the pain."
(It's a phrase I took from an excellent noir story)


-- 
Bruno Medeiros - MSc in CS/E student
http://www.prowiki.org/wiki4d/wiki.cgi?BrunoMedeiros#D

On Fri, 05 Jan 2007 14:00:03 +0100, Don Clugston wrote:

> 
> POKE 53280,0: POKE 53281,0
> Those were the days.

Oh... making the background and border black.  Those were indeed the days!

I moved to 6510 assembler eventually and started having fun with raster interrupts, setting the vic II to operate in different modes on different scan lines. Those days were so fun! I never got extremely far into such low-level things, but even the beginnings were full of wonder. :)

-JJR

Bruno Medeiros wrote:
> C/C++, Java and C#.
> 
> C/C++ is the one I'm wanting to be replaced by D.

The "one"?  Don't C and C++ count as two languages?  :-)

Stewart.

Walter Bright wrote:
> I just want to know the primary one.

Prior to D I would use (read: have used - I didn't do too much "serious"
programming) C++ for bigger projects (not too many of those) and Ruby for quick
scripts and the like.

Nowadays I use D for both. It's the language I'm most proficient in.

-- 
Remove ".doesnotlike.spam" from the mail address.

Frits van Bommel wrote:
> Glen Perkins wrote:
> 
>> C++'s gotcha-oriented programming
> 
> Quite possibly the best description of C++ I've ever seen :).

Probably, this ought to be chiseled in stone, and hung up above the door to Stroustrup's room.

If there ever was a phrase that exactly described my problem with C++, this is it.

-- And, while I previously voted "Java was my previous language", the real truth is that I always was dissatisfied with interpreted languages, and the only serious alternative seemed to be C(++), so finding D was like stumbling upon an oasis after 500 miles of biting sand.

Sean Kelly wrote:
> Pragma wrote:
> 
>> I cut my teeth on C64 Basic
> 
>> (*I see that I'm not alone here - it's like those things were built to train new coders)
> 
> I remember being so excited when the C64 magazines arrived in the mail--a friend and I would spend all day entering the printed code to play the new game they contained.  It wasn't my first experience with programming, but it was certainly one of the most significant.

Oh, the days!

To date, my biggest computing mistake was to not buy the C64. I had bought the VIC-20, and the 64 came out about a month later. I was always waiting for the follower to the 64, which "never" came. (The 128, years later never proved to be a real successor.)

At the time I had two worries: the (Microsoft!!!!) basic on the VIC was pretty arcane, no named subroutines with parameters, no proper renumbering of program lines, not to speak of switch statements and the like. The second worry was, I grew increasingly aware of the need of a formal, academic education in programming. For example, I had read several texts on programming where Recursion was mentioned. But, in all of them the only real example of recursion was the Fibonacci numbers. Not very real-world connected. Stuff like linked lists, priority queues,  unrolling versus compiling, were not familiar despite vigorous efforts.

My biggest personal feat (IMHO) was when I found an issue of the German CHIP magazine on the newsstand, and it boasted a "relocatable machine code monitor for the C64". They explicitly said it won't work on the VIC-24: too little memory, problems with address space, and of course a different CPU.

Earlier I had bought a 16k extension RAM card, mail order from Germany, but the magazine declared I still couldn't use the program on my VIC.

(OT: Heh, at the time, one couldn't buy a modem in Germany. They were considered "militarily dubious", or some such, so Germany became the last country in Europe to become "networked". Of course, 15 years later, the Internet simply flooded the continent.)

I think I stood some 2 hours at the magazine shelf in the bookstore, and finally decided "it is doable".

The program listing was some 8 spreads of tightly typed decimal bytecodes, with an error check code at the end of each line. I had to invent my own input routine because the logic of the C64 routine was dependent "on the length of the self-modifying-code input buffer" or some such (sorry, don't remember the exact details off-hand anymore).

Having entered half of the program, I had to save it to cassette tape (I too was too poor to afford a Floppy Drive). Then I entered the other half, saved it on the cassette tape, then I figured out a way to load each half into the same session, and then save them both together on a separate tape cassette.

Off hand I don't remeber too many times I've seriously been as proud of myself as  when I got the machine code monitor to actually work on my VIC-24 when it really wasn't supposed to be possible. Man, if I could relive that feeling again!!

Walter Bright a écrit :
> 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.

My primary langage is C.
From time to time, I also use shell and Perl (I despise Perl), I did one project in C++ too.

If I had the choice, it would be D and Ruby.

Scala looks interesting too.

renoX

My favorite language is Visual Basic 6.0 for Desktop and PHP for Web
Now i still learn D to improve my basic in OOP.
I am interesting in C# for my next web programming with ASP.NET
Also i am interesting with Haxe for SWF Flash
JAVA, C# and D help me a lot in understanding OOP style.