From: mwoehlke <mwoehlke@tibco.com>
To: cygwin-talk@cygwin.com
Subject: Re: how come #include "*.cpp" works?
Date: Thu, 18 May 2006 19:10:00 -0000 [thread overview]
Message-ID: <e4igm1$jq2$1@sea.gmane.org> (raw)
In-Reply-To: <010101c67aa9$49187880$a501a8c0@CAM.ARTIMI.COM>
Dave Korn wrote:
> On 18 May 2006 19:28, mwoehlke wrote:
>>> Something like this?
>> (moved below)
>>
>> Hey, that's pretty slick... thanks!
>
> :) It's a fairly standard technique.
Right, I *was* pretty sure I was trying to re-invent the wheel, which is
why I asked ;-).
>> Upon further thought, I may actually do something with my Makefile and
>> auto-generation of some file, but I think I'm still going to use part of
>> this. (Having an entire class declaration inside of a macro kind-of rubs
>> me wrong ;-). Also, I want to keep each class in its own header.)
>
> Yep, it's certainly a little ugly, but it serves to illustrate the
> technique; feel free to adapt and mutate to best serve your own purposes!
Thanks again!
--
Matthew
Hey, buddy, if it's OT, TITTTL!
next prev parent reply other threads:[~2006-05-18 19:10 UTC|newest]
Thread overview: 17+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <44638BED.5020009@telenet.be>
[not found] ` <4463A0D4.1060006@cygwin.com>
2006-05-17 15:52 ` mwoehlke
2006-05-17 16:00 ` Dave Korn
2006-05-17 16:28 ` Igor Peshansky
2006-05-17 16:57 ` Dave Korn
2006-05-18 14:46 ` mwoehlke
2006-05-18 16:59 ` Jason Alonso
2006-05-18 17:24 ` Dave Korn
2006-05-18 18:28 ` mwoehlke
2006-05-18 18:31 ` Dave Korn
2006-05-18 19:10 ` mwoehlke [this message]
2006-05-24 16:03 ` mwoehlke
2006-05-24 17:14 ` Dave Korn
2006-05-24 17:28 ` Igor Peshansky
2006-05-24 17:51 ` Dave Korn
2006-05-24 18:36 ` mwoehlke
2006-05-24 18:17 ` mwoehlke
2006-05-17 17:01 ` Dave Korn
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='e4igm1$jq2$1@sea.gmane.org' \
--to=mwoehlke@tibco.com \
--cc=cygwin-talk@cygwin.com \
/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).