Re: is typecasting return from malloc required?
- From: Keith Thompson <kst-u@xxxxxxx>
- Date: Wed, 10 Aug 2005 02:37:58 GMT
"John Bode" <john_bode@xxxxxxxxxxx> writes:
> E. Robert Tisdale wrote:
[...]
>> You code is generally more valuable
>> if it will compile a either C or C++.
>> We do this regularly.
>>
>
> You mean you regularly write code that's a ridiculously small subset of
> C and C++? You don't use classes, or templates, or any stdio routines?
> What, exactly, is the value of such a truncated language?
To be fair, C's <stdio.h> interface is included in C++ (I think the
header name is something like <cstdio>). The intersection of C90 and
C++ is actually pretty close to full C.
This doesn't imply that restricting yourself to that intersection is
worthwhile.
--
Keith Thompson (The_Other_Keith) kst-u@xxxxxxx <http://www.ghoti.net/~kst>
San Diego Supercomputer Center <*> <http://users.sdsc.edu/~kst>
We must do something. This is something. Therefore, we must do this.
.
- Follow-Ups:
- References:
- is typecasting return from malloc required?
- From: ceo
- Re: is typecasting return from malloc required?
- From: E. Robert Tisdale
- Re: is typecasting return from malloc required?
- From: Keith Thompson
- Re: is typecasting return from malloc required?
- From: E. Robert Tisdale
- Re: is typecasting return from malloc required?
- From: John Bode
- is typecasting return from malloc required?
- Prev by Date: Re: Defining errors and success in functions
- Next by Date: Re: Storing info for cards
- Previous by thread: Re: is typecasting return from malloc required?
- Next by thread: Re: is typecasting return from malloc required?
- Index(es):
Relevant Pages
|