6 Jan
2006
6 Jan
'06
3:41 p.m.
On Fri, 6 Jan 2006 16:41:47 -0500 (EST)
der Mouse <mouse at rodents.montreal.qc.ca> wrote:
Furthermore, unless you're working on a big team on a huge
project, what language is used for 'larger projects' doesn't
matter that much. You code it in what's appropriate. And for
lots of small-micro projects, assembly language is fine.
Anything with big stack overheads just sucks the resources right
out the hardware. Plus, in my case at least, I am a hardware
oriented person and get annoyed by abstractions. The reset
vector is MINE. I like to KNOW where my data is getting stored,
etc. I like to know that when a button is pressed, my debounce
routine will do what it's supposed to. And an oscilloscope is a
software debugging tool, if used right. For some software, the
first thing you write is the bit of code that toggles an I/O port
high and low to get things started.
These times
are gone - assembler is irrelevant for larger projects,
I'm not sure, at least not unless you restrict which kinds of projects
you're talking about. I recently finished playing one of the Ratchet &
Clank games for the PlayStation2, and watched the embedded making-of
video. According to that, their game engine is millions of lines of
assembly. (Unless I misunderstood, of course - I don't have it at
ready hand to rewatch - but it seems unlikely.)
/~\ The ASCII der Mouse
\ / Ribbon Campaign
X Against HTML mouse at rodents.montreal.qc.ca
/ \ Email! 7D C8 61 52 5D E7 2D 39 4E F1 31 3E E8 B3 27 4B