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.


Sean

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>

Chronological:

Perl
C++
C
PHP
D
Java
Rebol
Scheme

Primarily: C++

I have been happily using D for systems programming for 4 years :D. Long Live D!

Charlie

Walter Bright wrote:

> I also know that many of you are handy with multiple diverse languages, I just want to know the primary one.

C++ and Java

"Sean Kelly" <sean@f4.ca> wrote in message news:enhbp2$1vpv$1@digitaldaemon.com...
> 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.
>
>
> Sean

Remember entering the code for sprites? I'd spend half the morning typing a screenful of 0s and 1s, only to run the thing and discover my sprites were missing a limb or two. But you doggedly persisted, and were so chuffed with the end result, even though none of it was of your own design. I'd love to recapture that feeling.

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>

Primary Delphi With a good portion of C/C++

Asm was too high-level for me -> Verilog.

But after a decade, Verilog became boring -> Vera.

Both these languages excel at bit-level manipulations and at user space thread creation/manipulation with their built-in cooperative non-preemptive scheduler primitives.

> Asm?
> C++?
> C?
> None (D's your first language)?
> Java?
> C#?
> Python?
> Lisp?
> Ruby?
> Delphi?
> Perl?
> Cobol? <g>

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

POKE 53280,0: POKE 53281,0
Those were the days.
A lot of my early programming was refactoring the code while typing it in because I was such a slow typist.

I never used C64 BASIC much -- I switched to asm very quickly because it was higher level (!) I wrote my own editor/assembler, which let me have labels and variable names more than 2 characters long. It booted off a cassette drive in 15 seconds using a turboload routine (I was too poor to own a disk drive). It's still one of the programs I'm proudest of.

Don Clugston wrote:
> 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.
>>
>>
>> Sean
> 
> POKE 53280,0: POKE 53281,0
> Those were the days.
> A lot of my early programming was refactoring the code while typing it in because I was such a slow typist.
> 
> I never used C64 BASIC much -- I switched to asm very quickly because it was higher level (!) I wrote my own editor/assembler, which let me have labels and variable names more than 2 characters long. It booted off a cassette drive in 15 seconds using a turboload routine (I was too poor to own a disk drive). It's still one of the programs I'm proudest of.
> 

15 seconds?  Now *that's* impressive.  I recall waiting for some games to load via tape that took 2-3 *minutes*.

-- 
- EricAnderton at yahoo

Walter Bright skrev:
> 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 hobby trail:
  Basic -> 68k asm -> Pascal -> D

My earn-$-for-a-living trail:
  Pascal -> VB -> Objective-C -> C

My university studies trail:
  C -> C++ -> Lisp -> Java


What I always liked better with Pascal over C was that for the general case it made life much simpler, and code length shorter. And when needed inline asm is just so much better in Pascal.

Two treats D give me now; less code, and raw power when I want to, not because I have to.


// Fredrik Olsson

Sean Kelly wrote:
> JohnC wrote:
>>
>> But I recall programming my Sega SC-3000 in Basic, and later at high school commanding a "turtle" around the screen with the Logo language. Those were the days! 
> 
> Ah, the Logo hokey-pokey:
<snip>

ObD:

fd 200
rt 90
fd 30
rt 90
pu
fd 30
pd
fd 70
arc 180 70
arc 180 100
fd 70
pu
fd 30
rt 90
pd
fd 30
rt 135
pu
fd 20
setfloodcolor [255 0 0]
fill

(Note: a few of these commands aren't standard Logo, but MswLogo.)

Stewart.