From: "Pedro de Medeiros" <pedrovmm+lists@gmail.com>
To: Glynn Clements <glynn@gclements.plus.com>
Cc: Linux C Programming List <linux-c-programming@vger.kernel.org>
Subject: Re: various meanings of static
Date: Mon, 25 Jun 2007 20:01:32 -0300 [thread overview]
Message-ID: <38511efb0706251601n28622266k661db6c949be50cc@mail.gmail.com> (raw)
In-Reply-To: <18048.13578.542604.949301@cerise.gclements.plus.com>
On 6/25/07, Glynn Clements <glynn@gclements.plus.com> wrote:
>
> Using the preprocessor to create a project-specific language is seldom
> as good an idea as it may seem at the time, as you tend to end up with
> code which only the author understands.
>
> In general, to be able to work on a C source file should only require
> knowledge of C along with the types, variables and functions used by
> that particular file. Having to be familiar with a large number of
> project-specific conventions and idioms before you can touch anything
> tends to result in code which is hard to maintain.
Yes, now I agree.
Well, if macros are not worse than __attribute__ declarations for
machine-readability and if you acknowledge their usefulness, then
maybe you should have given the reason above in the first place. ;-)
Cheers,
Pedro.
prev parent reply other threads:[~2007-06-25 23:01 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2007-06-23 6:08 various meanings of static Shriramana Sharma
2007-06-23 12:55 ` Darío Mariani
2007-06-23 16:11 ` Glynn Clements
2007-06-24 21:08 ` Pedro de Medeiros
2007-06-25 21:35 ` Glynn Clements
2007-06-25 23:01 ` Pedro de Medeiros [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=38511efb0706251601n28622266k661db6c949be50cc@mail.gmail.com \
--to=pedrovmm+lists@gmail.com \
--cc=glynn@gclements.plus.com \
--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 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 NNTP newsgroup(s).