Back to General and Gameplay Programming

malloc -> new, realloc -> ???

Wildfire · 2002-12-06T03:57:36

Just something I got curious about... I know I''m supposed to use ''new'' in C++ rather then malloc. (which makes sense, since it''s a lot easier, typesafe etc. =) However, there does not seem to be a simple to use substitution for realloc. I know, "don''t use realloc, it''s bad will cause memory fragmentation, etc. blabla", but there''s situations where it''s simply impossible to predetermine how much data there''ll be. (Unless you invent a foolproof way to figure out how much userinput you''ll get (statistics? ) My usual way is -new temporaryArray[newSize] -copy old data to temporaryArray -insert new data to temporarArray -delete oldArray -oldArray.pointTo-> temporaryArray Anybody got better ideas, how to speed up the process? (programming, not execution).

General and Gameplay Programming Programming

Started by Wildfire December 05, 2002 09:33 AM

12 comments, last by Wildfire 21 years, 4 months ago

leroy

122

December 05, 2002 04:31 PM

Oops, the code part in my previous post is wrong. Sorry about that. Don''t know how to fix it...

Evil Bill

126

December 05, 2002 04:47 PM

[off topic]
< = <
> = >
[/off topic]

Member of the Unban Mindwipe Society (UMWS)

msn12b

390

December 05, 2002 08:09 PM

quote:Original post by SabreMan
You''re being melodramatic. There''s nothing wrong with using the standard containers. For the very few scenarios you need to handle dynamic reallocation, then you build a custom container for your purposes.

Eh.

MSN

angryzenmaster @ livejournal

SabreMan

504

December 06, 2002 03:57 AM

quote:Original post by msn12b
Eh.

"Very few". As in "it doesn''t happen that often". OK?

malloc -> new, realloc -> ???

This topic is closed to new replies.

Popular Topics

Recommended Tutorials

malloc -> new, realloc -> ???

This topic is closed to new replies.

Popular Topics

Recommended Tutorials

Reticulating splines