Tips on gaining proficiency in C

[AB]

Hi,

Regret the fact that this post may be slightly OT to c.l.c, but I am sure
that people there would give GREAT advice...

I am working as a QA (Automation), which generally involves writing mundane
Perl scripts for automated testing of a C Utility.

Bored with the kind of work I am doing, I would love to learn C Programming
(I have theoretical knowledge, thanks to a Bachelor's in CS), with the
intention of, to start with, learning enough to enable me dabble in systems
programming (Linux/Unix) (and hopefully, a job switch ...quickly :) )

I have a few books

- Design of the Unix OS, Bach
- APUE , (Richard Stevens)
- Network Programming (Richard Stevens)

Which I read now and then.

I have also gone through the C Faqs (All of it), but naturally, since I
haven't actually coded, it is not very useful.

Request suggestions/tips/hints on
- how I could go about getting some proficiency in C/Systems.
- Any suitable *projects* which would be worth doing (I tried sourceforge),
- the order (If there is any .. :) in which the above material is best read.
- (Any pointers to other good books are welcome, too ! )
Thanks a lot !

Abhi

[Alwyn]

In article <BF***********@ news.oracle.com >, AB
<ma************ @yahoo.dot.com> wrote:

I have a few books

- Design of the Unix OS, Bach
- APUE , (Richard Stevens)
- Network Programming (Richard Stevens)

Which I read now and then.

Excellent books all three, but how about adding another classic to the
list: 'The C Programming Language' (2nd ed.) by Kernighan and Ritchie?
Alwyn

[Tabrez Iqbal]

AB <ma************ @yahoo.dot.com> wrote in message news:<Fj******* ******@news.ora cle.com>...

Alwyn wrote:

In article <BF***********@ news.oracle.com >, AB
<ma************ @yahoo.dot.com> wrote:

I have a few books

- Design of the Unix OS, Bach
- APUE , (Richard Stevens)
- Network Programming (Richard Stevens)

Which I read now and then.

Excellent books all three, but how about adding another classic to the
list: 'The C Programming Language' (2nd ed.) by Kernighan and Ritchie?

Aah yes ! The Bible .. Shouldn't have missed that one.

Will be rushing to the bookstore immediately.

Thanks
Abhi

Along with TCPL by Kernighan and Ritchie, also pick-up the Answer Book
to the same book by Tondo. completing the exercises of K&R with the
help of the Answer Boor will give you lots of confidence.

tabrez

[Billy N. Patton]

AB wrote:

Hi,

Regret the fact that this post may be slightly OT to c.l.c, but I am
sure that people there would give GREAT advice...

I am working as a QA (Automation), which generally involves writing
mundane Perl scripts for automated testing of a C Utility.
If you write in perl, learning c will be NO problem. They are very
close. You could "almost" get perl code to compile in c by removing the
$ from scalars. %'s and @'s and regexp will be a different problem.

THere a ton of free libraries available. I have been writing in c and
perl for @ 12 years. I'm switching to C++ for everything except the
simplest of scripts. (long story but perl version is a major problem
here at work)
Bored with the kind of work I am doing, I would love to learn C
Programming (I have theoretical knowledge, thanks to a Bachelor's in
CS), with the intention of, to start with, learning enough to enable me
dabble in systems programming (Linux/Unix) (and hopefully, a job switch
...quickly :) )

I have a few books

- Design of the Unix OS, Bach
- APUE , (Richard Stevens)
- Network Programming (Richard Stevens)

Which I read now and then.

I have also gone through the C Faqs (All of it), but naturally, since I
haven't actually coded, it is not very useful.

Request suggestions/tips/hints on
- how I could go about getting some proficiency in C/Systems.
- Any suitable *projects* which would be worth doing (I tried
sourceforge), - the order (If there is any .. :) in which the above
material is best read.
- (Any pointers to other good books are welcome, too ! )
Thanks a lot !

Abhi

--
___ _ ____ ___ __ __
/ _ )(_) / /_ __ / _ \___ _/ /_/ /____ ___
/ _ / / / / // / / ___/ _ `/ __/ __/ _ \/ _ \
/____/_/_/_/\_, / /_/ \_,_/\__/\__/\___/_//_/
/___/
Texas Instruments ASIC Circuit Design Methodlogy Group
Dallas, Texas, 214-480-4455, b-******@ti.com

[Malcolm]

"AB" <ma************ @yahoo.dot.com> wrote

(I have theoretical knowledge, thanks to a Bachelor's in CS), with the
intention of, to start with, learning enough to enable me dabble in systems programming (Linux/Unix) (and hopefully, a job switch ...quickly :) )

If you have a degree in computer science then learning a new language
shouldn't be a problem. Simply pick up a primer and go.
To learn all the minutae of the standard is very difficult, but you don't
need this, just as you don't need a degree in linguistics to speak English
competently (though you might use a should for a would occasionally).

[Randy Howard]

In article <42************ **************@ posting.google. com>, tabrez19
_i@rediffmail.c om says...

Along with TCPL by Kernighan and Ritchie, also pick-up the Answer Book
to the same book by Tondo. completing the exercises of K&R with the
help of the Answer Boor will give you lots of confidence.

Technically this one isn't necessary, as web sites with answers to the
book's exercises are available on the web, but not all are authoritative.
If the OP is trying to save money, that one could be omitted. More to
his original posts, enquiries to c.l.c about troubles with K&R exercise
problems are never considered OT there.

--
Randy Howard (To reply, remove FOOBAR)

[Randy Howard]

In article <BF***********@ news.oracle.com >, ma************@ yahoo.dot.com
says...

Request suggestions/tips/hints on
- how I could go about getting some proficiency in C/Systems.
You have a lot of good answers so far, mostly consisting of "practice"
and repeat. That is good advice, it's really the only way until
someone figures out to make a potion which can be injected in the
arm to short-circuit the "experience " requirement.

Since you are working in QA and want to get into development (that
is a relatively common career path btw), you might consider asking
one of the people currently writing code for which you are doing
QA work to let you look at the source after you get some of the
"rust" knocked off from the books you plan to study. Read it,
understand it, compile it, etc. You might even find some good bugs
to make the boss happy (and the programmer less so) during the
process. Since the code represents a project for which you are
familiar, provided it is not overly complicated (the use of "utility"
in your description implies that it is not), it should make for a
decent way to get your feet wet with code that is already up and
running.
- Any suitable *projects* which would be worth doing (I tried sourceforge),
Sourceforge has some very good open source projects available, it also a
very large number of terrible ones, or ones that somebody thought would be
a good idea and never completed (or even started). It's a shame it does
not seem to get pruned out over time, but I digress.

One option is to google the web for C programming course homework assignments
once you have mastered the exercises in K&R. The other is to simply think
up programs that would be handy to have and implement them.
- (Any pointers to other good books are welcome, too ! )

C Traps and Pitfalls by Koenig is brief, but full of useful information in
a short space. The c.l.c FAQ is of course a requirement, but hopefully
you are already planning on reading it in total (not just looking for answers)
as well.

--
Randy Howard (To reply, remove FOOBAR)
"At the core of liberalism is the spoiled child - miserable,
as all spoiled children are, unsatisfied, demanding, ill-
disciplined, despotic and useless. Liberalism is a philosophy
of sniveling brats." -- P. J. O'Rourke

[Michael Wojcik]

In article <41************ **@ti.com>, "Billy N. Patton" <b-******@ti.com> writes:

If you write in perl, learning c will be NO problem. They are very
close.
This must be the largest value for "very close" ever recorded.

Perl is an object-oriented high-level scripting language. C is
none of these.

Perl has built-in support for threading, embedded documentation, hash
tables, lists, operator contexts (scalar and list), two forms of
scope (lexical and dynamic), labelled flow control, alternative forms
of "if" statements (unless and elsif), modifier statements (where
body preceeds flow control), computed goto, non-local goto (goto
&name), regular expression pattern matching, and lambdas (run-time
anonymous subroutines). None of those are in C.

Perl has scads of special variables and operators which are not in
C, particularly for string manipulation.

Perl has two different string types, one with some C-like escape
sequences plus various ones not in C, the other without them. It
permits newlines in string constants. It has another entire quoting
mechanism which is completely foreign to C. Perl has a syntax for
numeric literals which is not in C (using the underscore character).

Perl has tons of standard modules which in effect give it a standard
"library" that's far larger and more ambitious than the C standard
library.
You could "almost" get perl code to compile in c by removing the
$ from scalars.

This is only true of the most trivial and non-idiomatic Perl code.
I've never seen published Perl code that did anything useful that
was even close to C.

Perl adopted some of its operators from C (actually, Larry Wall
likely adopted them from the more popular Unix shells, which adopted
them from C), but it's really very little like C.

--
Michael Wojcik mi************@ microfocus.com

Auden often writes like Disney. Like Disney, he knows the shape of beasts --
(& incidently he, too, might have a company of artists producing his lines) --
unlike Lawrence, he does not know what shapes or motivates these beasts.
-- Dylan Thomas

[Willem]

Michael wrote:
) Perl is an object-oriented high-level scripting language. C is
) none of these.
)
) <...>
)
) Perl adopted some of its operators from C (actually, Larry Wall
) likely adopted them from the more popular Unix shells, which adopted
) them from C), but it's really very little like C.

Well, one could claim that most C code would run in perl with very little
modification. One could also claim that for most shell scripts, most awk
scripts, most sed scripts, and probably several other ways of programming.
SaSW, Willem
--
Disclaimer: I am in no way responsible for any of the statements
made in the above text. For all I know I might be
drugged or something..
No I'm not paranoid. You all think I'm paranoid, don't you !
#EOT

[AB]

Randy Howard wrote:

In article <BF***********@ news.oracle.com >, ma************@ yahoo.dot.com
says...

Request suggestions/tips/hints on
- how I could go about getting some proficiency in C/Systems.

You have a lot of good answers so far, mostly consisting of "practice"
and repeat. That is good advice, it's really the only way until
someone figures out to make a potion which can be injected in the
arm to short-circuit the "experience " requirement.

<OT>
a-la Matrix ... :)
</OT>
Since you are working in QA and want to get into development (that
is a relatively common career path btw), you might consider asking
one of the people currently writing code for which you are doing
QA work to let you look at the source after you get some of the
"rust" knocked off from the books you plan to study. Read it,
understand it, compile it, etc. You might even find some good bugs
to make the boss happy (and the programmer less so) during the
process. Since the code represents a project for which you are
familiar, provided it is not overly complicated (the use of "utility"
in your description implies that it is not), it should make for a
decent way to get your feet wet with code that is already up and
running.

Thanks for the advice! My usage of the term "utility" is downright
misleading. It is more of a major project with 10+ full time developers.

- Any suitable *projects* which would be worth doing (I tried sourceforge),

Sourceforge has some very good open source projects available, it also a
very large number of terrible ones, or ones that somebody thought would be
a good idea and never completed (or even started). It's a shame it does
not seem to get pruned out over time, but I digress.

One option is to google the web for C programming course homework assignments
once you have mastered the exercises in K&R. The other is to simply think
up programs that would be handy to have and implement them.

- (Any pointers to other good books are welcome, too ! )

C Traps and Pitfalls by Koenig is brief, but full of useful information in
a short space. The c.l.c FAQ is of course a requirement, but hopefully
you are already planning on reading it in total (not just looking for answers)
as well.

I already have read the C FAQs end to end, but most of it passed through
due to the fact that I did not actually write code when reading.

Thanks to everyone for their tips and suggestions !

Regards
Abhi