On Wed, Jul 13, 2005 at 01:28:14AM +0200, Falk Hueffner wrote: > You're missing my point; size_t was just an example, whoever does this > will know what the correct type is for their system. All I'm saying > is that we shouldn't go to the trouble to document and kick along some > language extension, maybe even miss some optimization because of it, > when there's a perfectly fine alternative to it for the user.
Having the user add stupid, potentially breakable casts which decrease readability just because the standard says the compiler is allowed to be a prick is not necessarily a good idea. I don't really see the point of breaking or even warning on pretty much every memory management or garbage collection code out there. OG.
