Re: Why We Use C Than C++...
- From: "Imre Palik" <firstname.lastname.ext@xxxxxxxxxxxxxxxxxxxxxx>
- Date: 13 Jan 2006 18:25:35 +0100
Richard Heathfield <invalid@xxxxxxxxxxxxxxx> writes:
> > Ok, and then write me a working equivalent to the C++ template
> > mechanism... ;o)
>
> Why bother?
To spare a few hundred lines of code?
Ok, I used macros with type arguments to this end before. But I
tended to be yelled at on code reviews for this. I still have no idea
why ... :-)
ImRe
.
- Follow-Ups:
- Re: Why We Use C Than C++...
- From: Richard Heathfield
- Re: Why We Use C Than C++...
- References:
- Why We Use C Than C++...
- From: sonugeetha@xxxxxxxxx
- Re: Why We Use C Than C++...
- From: Richard Heathfield
- Re: Why We Use C Than C++...
- From: Dag-Erling Smørgrav
- Re: Why We Use C Than C++...
- From: henryk . mueller
- Re: Why We Use C Than C++...
- From: Dag-Erling Smørgrav
- Re: Why We Use C Than C++...
- From: henryk . mueller
- Re: Why We Use C Than C++...
- From: Richard Heathfield
- Re: Why We Use C Than C++...
- From: henryk . mueller
- Re: Why We Use C Than C++...
- From: Richard Heathfield
- Why We Use C Than C++...
- Prev by Date: Re: How does free() know how many elements should be freed in a dynamic array?
- Next by Date: Re: Function that returns a pointer to a function of the same signature?
- Previous by thread: Re: Why We Use C Than C++...
- Next by thread: Re: Why We Use C Than C++...
- Index(es):
Relevant Pages
|