From: Uwe Kindler <uwe_kindler@web.de>
To: John Dallaway <john@dallaway.org.uk>
Cc: ecos-devel@sourceware.org
Subject: uSTL config.h clash
Date: Sat, 29 Aug 2009 16:58:00 -0000 [thread overview]
Message-ID: <4A995E22.9010606@web.de> (raw)
Hi John,
if I move the all uSTL headers except of ustl.h into an ustl
subdirectory, then I need to touch almost all include directives in the
ustl header and source files. I.e. in unew.c I would replace #include
"unew.h" by #include "ustl/unew.h". Did I understand this right?
Another solution would be to rename config.h into something like
ustlconfig.h and rename all include directives that include config.h
into #include "ustlconfig.h". This would avoid a name clash but the ustl
headers would still pollute the toplevel include directory.
What would you prefer?
Regards, Uwe
next reply other threads:[~2009-08-29 16:58 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2009-08-29 16:58 Uwe Kindler [this message]
2009-08-29 19:43 ` John Dallaway
2009-08-29 20:26 ` John Dallaway
2009-08-29 21:25 ` Uwe Kindler
2009-08-29 21:30 ` Uwe Kindler
2009-08-30 17:39 ` John Dallaway
-- strict thread matches above, loose matches on Subject: below --
2009-08-28 16:33 John Dallaway
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=4A995E22.9010606@web.de \
--to=uwe_kindler@web.de \
--cc=ecos-devel@sourceware.org \
--cc=john@dallaway.org.uk \
/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).