And what would you cast the void* back to afterwards?

Post #100,616 by tuberculosis 5/6/03 5:15:51 PM 8/21/07 6:38:46 AM Reply	And what would you cast the void* back to afterwards? "Packed like lemmings into shiny metal boxes. Contestants in a suicidal race." - Synchronicity II - The Police Edited by tuberculosis Aug. 21, 2007, 06:38:46 AM EDT Expand All History
Post #100,631 by Simon_Jester 5/6/03 6:47:54 PM Reply	Yeah, you'd have to test for the type... or assign it to a base class pointer that the two types are dervived from. Of course, there are cases were you'd have to the for type for your max macro. sprintf("%d", max(long, float));
Post #100,644 by tuberculosis 5/6/03 9:15:43 PM 8/21/07 6:39:11 AM Reply	Aaaaaahhhhhhh! sprintf("%d", max(long, float)); Why don't you just juggle torches while you gas up your car? First, you're short an argument to sprintf - you forgot the destination buffer. Second, the xxxxf family (scanf, printf, and their variants), have no place in C++. Use strstreams. char buffer[50]; ostrstream ost(buffer,sizeof(buffer)); ost << (max(aLong, aFloat)) << ends; "Packed like lemmings into shiny metal boxes. Contestants in a suicidal race." - Synchronicity II - The Police Edited by tuberculosis Aug. 21, 2007, 06:39:11 AM EDT Expand All History
Post #100,647 by Simon_Jester 5/6/03 9:46:44 PM Reply	chuckle d00d, that was off the cuff. It wasn't meant to be code perfect - just to illustrate a problem with max. Second, use stringstreams. strstreams are the old style char* stuff, iirc. You have to unfreeze any .str() you create via them...yuk.
Post #100,672 by tuberculosis 5/7/03 1:00:51 AM 8/21/07 6:39:47 AM Reply	Oh, you illustrated several problems max was the least of them. Thanks for the tip on the updated streams. I can't say they're an improvement though. Item 1: YTF did they blend istream and ostream in stringstream? Can you use it as a queue? Will it block on reads or throw an exception? We already have pipes for this stuff. Item 2: The new version is written in terms of string. This is OK, but string does heap allocation all the time so for small buffers its likely to suck compared to stack memory. You'll note that in my code I don't need to call str or freeze as I already have the buffer. So it looks like streaming to a known memory location is no longer supported. So much for high performance code. Item 3: You can construct one with no buffer (it'll use a string) or a const string&. Nifty. Suppose I want to stream into my own string. I'll miss WriteStream on: myString. WTF are this people thinking? "Packed like lemmings into shiny metal boxes. Contestants in a suicidal race." - Synchronicity II - The Police Edited by tuberculosis Aug. 21, 2007, 06:39:47 AM EDT Expand All History

Welcome to IWETHEY!