From: Jan-Benedict Glaw <jbglaw@lug-owl.de>
To: linux-c-programming@vger.kernel.org
Subject: Re: C Newbie
Date: Mon, 13 Dec 2004 16:50:43 +0100 [thread overview]
Message-ID: <20041213155043.GY16958@lug-owl.de> (raw)
In-Reply-To: <BDE318F8.1618%dsessions@ionosphere.net>
[-- Attachment #1: Type: text/plain, Size: 1008 bytes --]
On Mon, 2004-12-13 10:01:28 -0500, Darren Sessions <dsessions@ionosphere.net>
wrote in message <BDE318F8.1618%dsessions@ionosphere.net>:
> I need to know (before I get flamed) if this is an appropriate spot to post
> questions on C programming or not and the very most newbie level. I'm
> attempting a transition from Perl and, while I understand a lot of the
> fundamentals of C, am having a hard time with string (char) manipulation.
Start asking. However, start a question with a new email, not by
pressing you email client's "reply" button and deleting any old text.
Hijacking threads is bad habit and makes proper email sorting a hard
challange...
MfG, JBG
--
Jan-Benedict Glaw jbglaw@lug-owl.de . +49-172-7608481 _ O _
"Eine Freie Meinung in einem Freien Kopf | Gegen Zensur | Gegen Krieg _ _ O
fuer einen Freien Staat voll Freier Bürger" | im Internet! | im Irak! O O O
ret = do_actions((curr | FREE_SPEECH) & ~(NEW_COPYRIGHT_LAW | DRM | TCPA));
[-- Attachment #2: Digital signature --]
[-- Type: application/pgp-signature, Size: 189 bytes --]
next prev parent reply other threads:[~2004-12-13 15:50 UTC|newest]
Thread overview: 11+ messages / expand[flat|nested] mbox.gz Atom feed top
2004-12-13 10:04 Assignment make pointers r_zaca
2004-12-13 10:10 ` Jan-Benedict Glaw
2004-12-13 14:51 ` Eric Bambach
2004-12-13 14:58 ` Eric Bambach
2004-12-13 15:01 ` C Newbie Darren Sessions
2004-12-13 15:50 ` Jan-Benedict Glaw [this message]
2004-12-13 16:03 ` Eric Bambach
2004-12-29 2:13 ` Defunct Processes Darren Sessions
2004-12-29 10:16 ` Jan-Benedict Glaw
2004-12-30 13:14 ` Daniel Souza
2004-12-13 15:47 ` Assignment make pointers Jan-Benedict Glaw
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=20041213155043.GY16958@lug-owl.de \
--to=jbglaw@lug-owl.de \
--cc=linux-c-programming@vger.kernel.org \
/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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.