From: Dan Kegel <dank@kegel.com>
To: Jonathan Wakely <jwakely.gcc@gmail.com>
Cc: tele <swojskichlopak@wp.pl>, gcc-help <gcc-help@gcc.gnu.org>
Subject: Re: Question, using gcc, forum.
Date: Sat, 5 Sep 2020 08:03:58 -0700 [thread overview]
Message-ID: <CAPF-yOYQKSUzY8gDnDxqJkuLnC0CwV7tt32=+BrYzC3885VVoA@mail.gmail.com> (raw)
In-Reply-To: <CAH6eHdTZS9=mWpH96z-gz4Kx=p=SnQQjx-a+AAMHODGetPEFnw@mail.gmail.com>
How about K&R?
https://en.m.wikipedia.org/wiki/The_C_Programming_Language
That did it for me. You can pick up a used 2nd edition for cheap, I'm sure.
Similarly, D&K (sharing one author) is a wonderful introduction to Go.
https://www.gopl.io/
- Dan
Jonathan Wakely via Gcc-help <gcc-help@gcc.gnu.org> schrieb am Sa., 5.
Sept. 2020, 01:15:
> On Fri, 4 Sep 2020 at 23:51, tele via Gcc-help <gcc-help@gcc.gnu.org>
> wrote:
> >
> >
> > I am looking for a "forum" where I can find help in learning programming
> c.
> > Because the "manual" doesn't look great for me.
> >
> >
> > For example:
> > - Where is C manual ?
> > https://gcc.gnu.org/onlinedocs/
> >
> > Why there ?
> > https://www.gnu.org/software/gnu-c-manual/gnu-c-manual.html
>
> Because that's a completely separate project from GCC, it's just that
> they both happen to be under the GNU umbrella.
>
> It seems reasonable to link to the GNU C Manual from the GCC website,
> if we don't do so already.
>
>
> > For example:
> > https://www.gnu.org/software/gnu-c-manual/gnu-c-manual.html
> > https://tiswww.case.edu/php/chet/bash/bashref.html
> >
> > My description for an example of building a bicycle.
> > This looks like a description of the components that make up the bike.
> > I am especially concerned that the manual shows the gear, but it does
> not show if it is part of a larger set and where it is on the bike.
> > But maybe I am too stupid or blind because I do not see the tutorial on
> how to build a programs.
> >
> > For me, this is archeology in which I try to deduce something sensible
> from the ruins and sand.
> >
> > That's why I need someone who can help me get through the beginning a
> little.
> > Especially since the language is constantly evolving. Programming
> security too. And maybe someone has some programming advice on my own blog
> that I can't find in internet.
>
> My personal advice: Get a good book. Teaching C programming is not
> simple, and expecting to get it for free from a website is optimistic.
> If you want quality material, pay for it by supporting an established
> author of quality books.
>
>
prev parent reply other threads:[~2020-09-05 15:04 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <20200831201750.74266362@arch.localdomain>
[not found] ` <20200903232726.ba28157e5ee86c0dbd76f723@wp.pl>
2020-09-04 22:49 ` tele
2020-09-04 23:44 ` Question tele
2020-09-05 7:31 ` Question, using gcc, forum Kai Ruottu
2020-09-05 8:15 ` Jonathan Wakely
2020-09-05 15:03 ` Dan Kegel [this message]
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to='CAPF-yOYQKSUzY8gDnDxqJkuLnC0CwV7tt32=+BrYzC3885VVoA@mail.gmail.com' \
--to=dank@kegel.com \
--cc=gcc-help@gcc.gnu.org \
--cc=jwakely.gcc@gmail.com \
--cc=swojskichlopak@wp.pl \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for read-only IMAP folder(s) and NNTP newsgroup(s).