public inbox for gcc@gcc.gnu.org
 help / color / mirror / Atom feed
From: Jason Merrill <jason@cygnus.com>
To: Ildar Mulyukov <ildar@faki-campus.mipt.ru>
Cc: egcs@cygnus.com
Subject: Re: TODO: egcs-g++
Date: Sun, 11 Apr 1999 02:02:00 -0000	[thread overview]
Message-ID: <u9pv5bjzr7.fsf@yorick.cygnus.com> (raw)
In-Reply-To: <Pine.LNX.4.04.9904111239190.12263-100000@natalie.faki-campus.mipt.ru>

>>>>> Ildar Mulyukov <ildar@faki-campus.mipt.ru> writes:

 > On 11 Apr 1999, Jason Merrill wrote:
 >> Would someone explain to me what anonymous structs are good for?  It seems
 >> like a totally pointless extension.

 > Hey! That's simple.

OK, I get it.  Thanks.

 >> WRT cr/lf issues, in the current development sources cpplib handles them
 >> interchangeably, so you might try that out.

 > I checked out cvs version of egcs week ago. It could not handle CRLF
 > properly.

You need to configure with --enable-cpplib.

Jason

WARNING: multiple messages have this Message-ID
From: Jason Merrill <jason@cygnus.com>
To: Ildar Mulyukov <ildar@faki-campus.mipt.ru>
Cc: egcs@cygnus.com
Subject: Re: TODO: egcs-g++
Date: Fri, 30 Apr 1999 23:15:00 -0000	[thread overview]
Message-ID: <u9pv5bjzr7.fsf@yorick.cygnus.com> (raw)
Message-ID: <19990430231500.lB3jJnusxPKuWknUwxAtGbQqZjrQYoEAUwIC4607Ngc@z> (raw)
In-Reply-To: <Pine.LNX.4.04.9904111239190.12263-100000@natalie.faki-campus.mipt.ru>

>>>>> Ildar Mulyukov <ildar@faki-campus.mipt.ru> writes:

 > On 11 Apr 1999, Jason Merrill wrote:
 >> Would someone explain to me what anonymous structs are good for?  It seems
 >> like a totally pointless extension.

 > Hey! That's simple.

OK, I get it.  Thanks.

 >> WRT cr/lf issues, in the current development sources cpplib handles them
 >> interchangeably, so you might try that out.

 > I checked out cvs version of egcs week ago. It could not handle CRLF
 > properly.

You need to configure with --enable-cpplib.

Jason

  reply	other threads:[~1999-04-11  2:02 UTC|newest]

Thread overview: 42+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
1999-04-09 21:31 Ildar Mulyukov
1999-04-09 22:46 ` Alexandre Oliva
1999-04-10  1:00   ` Andi Kleen
1999-04-10 13:21     ` Joe Buck
1999-04-30 23:15       ` Joe Buck
1999-04-11  1:53     ` Ildar Mulyukov
1999-04-11 13:15       ` Joe Buck
1999-04-30 23:15         ` Joe Buck
1999-04-30 23:15       ` Ildar Mulyukov
1999-04-30 23:15     ` Andi Kleen
1999-04-11 23:44   ` Andris Pavenis
1999-04-30 23:15     ` Andris Pavenis
1999-04-30 23:15   ` Alexandre Oliva
     [not found] ` <m390c06h4d.fsf.cygnus.egcs@muc.de>
1999-04-11  1:40   ` Jason Merrill
1999-04-11  1:49     ` Ildar Mulyukov
1999-04-11  2:02       ` Jason Merrill [this message]
1999-04-30 23:15         ` Jason Merrill
1999-04-30 23:15       ` Ildar Mulyukov
1999-04-11  2:50     ` Andi Kleen
1999-04-11 13:51       ` Alexandre Oliva
1999-04-30 23:15         ` Alexandre Oliva
1999-04-30 23:15       ` Andi Kleen
1999-04-11  4:08     ` Tim Waugh
1999-04-12 13:11       ` Mumit Khan
1999-04-12 13:39         ` Zack Weinberg
1999-04-12 15:20           ` Gerald Pfeifer
1999-04-12 18:01             ` Jeffrey A Law
1999-04-30 23:15               ` Jeffrey A Law
1999-04-30 23:15             ` Gerald Pfeifer
     [not found]           ` <Pine.GSO.4.10.9904130014560.14974-100000.cygnus.egcs@alphard.dbai.tuwien.ac.at>
1999-04-12 20:48             ` Jason Merrill
1999-04-30 23:15               ` Jason Merrill
1999-04-30 23:15           ` Zack Weinberg
1999-04-13  7:15         ` Gavin Romig-Koch
1999-04-30 23:15           ` Gavin Romig-Koch
1999-04-30 23:15         ` Mumit Khan
     [not found]       ` <Pine.SUN.3.93.990412150105.700E-100000.cygnus.egcs@modi.xraylith.wisc.edu>
1999-04-12 20:56         ` Jason Merrill
1999-04-12 21:30           ` Jeffrey A Law
1999-04-30 23:15             ` Jeffrey A Law
1999-04-30 23:15           ` Jason Merrill
1999-04-30 23:15       ` Tim Waugh
1999-04-30 23:15     ` Jason Merrill
1999-04-30 23:15 ` Ildar Mulyukov

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=u9pv5bjzr7.fsf@yorick.cygnus.com \
    --to=jason@cygnus.com \
    --cc=egcs@cygnus.com \
    --cc=ildar@faki-campus.mipt.ru \
    /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).