Title: 샘플교재(테이프)를받아보고싶으신분은주소를기재하신후.아래의신청하기버튼을클릭하세요.
샘플테이프 신청자는 주소확인과 함께 무료로 교재
및 프로그램상담을 곧바로 받으실 수 있습니다.
On Mon, Feb 11, 2002 at 07:03:15PM -0800, Randolph Chung wrote:
> > Problem: gdb-5.1.1 doesn't configure, gives the following
> > error message:
> >...
> >checking for X... no
> >configure: error: *** Gdb does not support host
> > hppa1.1-unknown-linux-gnu
> >Configure in /usr/src/
Neal H Walfield <[EMAIL PROTECTED]> writes:
> > I didn't say it was difficult. It's easy. It's also silly. Why
> > should I worry all the time about such adaptation?
> >
> > How many languages do you want me to support?
> >
> > C++ is an *incompatible* extension of C. Extension yes, compat
> I didn't say it was difficult. It's easy. It's also silly. Why
> should I worry all the time about such adaptation?
>
> How many languages do you want me to support?
>
> C++ is an *incompatible* extension of C. Extension yes, compatible,
> no.
Just a weeks ago, you were arguing on one of
Adam Majer <[EMAIL PROTECTED]> writes:
> It is a lot more difficult for C++ parser to accomodate
> non-portable C code. IMO, all proper C code should compile with
> a C++ compiler.
I wonder what you think of C99 then?
Ryan
--
Ryan Golbeck <[EMAIL PROTECTED]>
Computer Science, University Of Wa
Adam Majer <[EMAIL PROTECTED]> writes:
> C++ is an _extention_ of C. IMHO, it is very easy for C programs to
> accomodate C++ [...]
I didn't say it was difficult. It's easy. It's also silly. Why
should I worry all the time about such adaptation?
How many languages do you want me to support
On Wed, Feb 13, 2002 at 12:37:00PM -0800, Thomas Bushnell, BSG wrote:
> Jeff Bailey <[EMAIL PROTECTED]> writes:
>
> > It's no harder or more complicated than making a header file work with
> > both K&R and ANSI, especially now that C++ is standardized. It's just
> > a matter of whether the author
Ah, the agony of defeat.
I'm throwing in the towel on this one. I did manage to compile gdb
for hppa using the parisc-linux.org code, but when I tried to make
the cross debugger for Hurd it wanted Mach headers for some reason.
So I copied my headers over from the Hurd box, and make just
blew up int
On Tuesday 12 February 2002 03:34, Thomas Bushnell, BSG wrote:
> I think that using #include in a C++ program is wrong for
> exactly the same reasons that using it in a Pascal program would be
> wrong.
Just a short quote from the 'Mach 3 server writer's guide', page 6:
Given that most servers
-
Alson Kemp [EMAIL PROTECTED]
Senior FAE, North CaliforniaW: 510-624-7184
Cirrus F: 510-252-6020
46831 Lakeview Blvd C: 408-981-6685
Fremont, CA 94538
-
Hi people!
I have been hacking an example-translator (based on the run-translator) which
uses io_read and io_seek. While the run-translator gave me the needed
prototypes for those two, I can't find something like a header on my whole
system.
I have gotten around to notice that these protos some
Jeff Bailey <[EMAIL PROTECTED]> writes:
> It's no harder or more complicated than making a header file work with
> both K&R and ANSI, especially now that C++ is standardized. It's just
> a matter of whether the authors wanted to do so or not.
No, no, no, you've missed the point entirely.
I coul
On Wed, Feb 13, 2002 at 08:22:22AM -0800, Thomas Bushnell, BSG wrote:
> The authors of cthreads were not trying to bind C++ people. Indeed,
> what they were doing was simply ignoring them. That is, they didn't
> say "ooh, here's a way to screw C++ people", they simply don't
> bother keeping trac
Ondrej Hurt <[EMAIL PROTECTED]> writes:
> Sorry but I can't help myself: I think that the one who wrote
> cthreads should be flamed for completely unnecessarily binding C++
> people to C (which they might think is crap)
The authors of cthreads were not trying to bind C++ people. Indeed,
what the
commence Ondrej Hurt quotation:
>> > > I think that using #include in a C++ program is wrong
>> > > for exactly the same reasons that using it in a Pascal program would
>> > > be wrong.
>> > C++ is designed to link with C libraries. Pascal is not. The
>> > argument doesn't follow.
>> Um, then
> > > I think that using #include in a C++ program is wrong
> > > for exactly the same reasons that using it in a Pascal program would
> > > be wrong.
> >
> > C++ is designed to link with C libraries. Pascal is not. The
> > argument doesn't follow.
> Um, then the C++ designers should be flamed
16 matches
Mail list logo
