OT What's next

On 11/30/06, Alan Gauld < alan.gauldbtinternet.com"> alan.gauldbtinternet.com> wrote:

"Amadeo Bellotti&quot; < amadeo.bellottigmail.com"> amadeo.bellottigmail.com> wrote

>; step two sites to learn anyone know where i can look
> up c programming for linux?

Ah! Now, if you'd said you were talking about a
Linux PC then there would be no question. C is
the only way to go.

The Linux documentation project has loads of stuff about
programming for Linux, but you need to learn C first.

My personal choices for books are:
1) The original C Language book by Kernighan & Ritchie
One of the finest programming tutorials ever written, great
for core C but useless for the library functions.
2) C The Complete Reference by Schildt. A very good tutorial
that also makes a good (albeit DOS oriented)&nbsp; reference manual.

Online I haven't seen anything outstanding for C but
then I haven't really looked at beginners tutorials because I
could already program C before the web was invented!

One thing - Don;t get sidetracked into C++. Its a whole
different ballgame, much more complex and unnecessary
if you want to go low level.

HTH,

Alan G.


>
> On 11/29/06, Terry Carroll < carrolltjc.com">carrolltjc.com &gt; wrote:
>;>
>&gt; On Wed, 29 Nov 2006, R. Alan Monroe wrote:
>;>
>&gt; > > Pure assembler on a PC involves a huge amount of work for even
>&gt; > > the most trivial task.
>;> >
>&gt; > Some useful assembly tips here:
>> > http://www.grc.com/smgassembly.htm
>>;
>> I never wanted to actually program assembly on the PC, but I did
>&gt; want to
>>; understand it (actually, I wanted to understand the Intel x86
>&gt; architecture, and there's no better way of doing that than learning
&gt;> the
>&gt; assembly language for a machine).&nbsp; I read Jeff Duntemann's
>> "Assembly
>&gt; language Step-by-Step,"&nbsp; http://duntemann.com/assembly.htm , and
>&gt; found it
>>; very useful, although I didn't actually try any programming.
>>;
>> I'm an old mainframe assembler language hack from way back in the
>&gt; IBM
>&gt; System/370 days (although in my last development job, I wrote more
>&gt; in
>>; machine code than in actual assembler), so I didn't really need or
>&gt; desire
>;> to do the practical aspects of actually writing x86 code; but I
>> felt that
>&gt; would have been a good book to get me there, had that been what I
>> wanted.
&gt;>
>;> A couple of years ago, I took a course in which I built a
>> rudimentary
>> computer around an Intel 8031 chip; and when I say "built," I mean
>&gt; built.
>;> It was a couple dozen components on a breadboard, with about only
>> about
>> 2Kbytes of memory, if I recall; I soldered or wire-wrapped every
>> connection. &nbsp;You really learn an architecture when you do that.
>> not that
>&gt; I remember much of it anymore, two years later.&nbsp; Not a route I
>>; recommend.
>> I needed a few credits to fill an obscure educational requirement,
>> though,
&gt;> and this was a fun way to do it.
>&gt;
>> _______________________________________________
>&gt; Tutor maillist&nbsp; -  ; Tutorpython.org">Tutorpython.org
>> http://mail.python.org/mailman/listinfo/tutor
>>;
>


--------------------------------------------------------------------------------


> _______________________________________________
> Tutor maillist&nbsp; -  ; Tutorpython.org">Tutorpython.org
> http://mail.python.org/mailman/listinfo/tutor
>


_______________________________________________
Tutor maillist&nbsp; -  ; Tutorpython.org"> Tutorpython.org
http://mail.python.org/mailman/listinfo/tutor