Return Styles: Pseud0ch, Terminal, Valhalla, NES, Geocities, Blue Moon. Entire thread

GONNA LEARN ME SOME COMPUTERS

Name: Anonymous 2009-02-27 14:52

Sup /prog/.

DUAL TOPIC:

I'm tryin' to design a roguelike and decided I'd make the attempt in Python since I have next to no programming experience and a high level language seemed like a good place to start.

1) Am I correct in this assumption, or should I just suck it up and learn C/C++/Haskell/something faster yet much more difficult to learn than Python?

2) I can't do shit until I at least understand the language, so suggest little things for me to program so I can figure out what the hell is going on, oh god how did this get here I am not good with computer

Name: Anonymous 2009-02-27 19:05

>>12
Which one, the first, or the second? The first is good if you're learning Forth. It's basic, but Forth has several low-level quirks that a person needs to know to write it effectively. It's a quick read, and a person with little to no knowledge of Forth would do well to read it before reading the second. A person with a general idea how to read Forth code who wasn't interesting in programming in Forth in the near future could skip the first book.

The second book is just great. It's about program design, from the perspective of a Forth expert. A combination of Forth's concatenative nature, its low-level foundation, and its interactivity yield design insights that were completely new to me, coming from a Lisp background and being schooled in typical fag languages. Where else do you get topics like Minimizing Control Structures (conditionals and such) and The Limits of Level Thinking (high-level/low-level program components)? Lots of things that are good to keep in mind in any language, but which are seldom well articulated.

Newer Posts
Don't change these.
Name: Email:
Entire Thread Thread List