From: "Dave Korn" <dave.korn@artimi.com>
To: "'not really'" <cygwin-talk@cygwin.com>
Subject: RE: how come #include "*.cpp" works?
Date: Wed, 17 May 2006 16:57:00 -0000 [thread overview]
Message-ID: <000701c679d2$f300d950$a501a8c0@CAM.ARTIMI.COM> (raw)
In-Reply-To: <Pine.GSO.4.63.0605171227040.17840@access1.cims.nyu.edu>
On 17 May 2006 17:28, Igor Peshansky wrote:
> On Wed, 17 May 2006, Dave Korn wrote:
>
>> On 17 May 2006 16:43, mwoehlke wrote:
>>
>>> Larry Hall (Cygwin) wrote:
>>>> This isn't a Cygwin specific problem so it's off-topic for this list.
>>>> Please find a better forum for such questions. If you feel you must
>>>> continue this discussion with a Cygwin crowd, then you can try the
>>>> cygwin-talk list.
>>>
>>> On that note, does anyone know of a good C++ forum? I have an
>>> interesting problem I'd like to see if anyone has any clever solutions
>>> for.
>>
>> You've piqued my curiousity now. Go on then, what's the C++ problem?
>
> Ditto.
>
>> (And for 5 bonus points for topicality, how can it be related to
>> hippos?)
>
> Heh? C++ has always been related to hippos. What do you think the .hpp
> extension stands for?
Oh wow, that's for 'hippo' is it? I always thought it stood for
<penelopepitstop> Haaayyy-ulppp! </penelope>
cheers,
DaveK
--
Can't think of a witty .sigline today....
next prev parent reply other threads:[~2006-05-17 16:57 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 [this message]
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
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='000701c679d2$f300d950$a501a8c0@CAM.ARTIMI.COM' \
--to=dave.korn@artimi.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).