Tasteless mimic of operator new: Call ctor

[dude_1967]

Lindley, I can't add to your rep any more because the box won't let me. Wants me to spread it around.

But you rock. All the other gurus too.

Bye, Chris.

[D_Drmmr]

There will be no corresponding calls to delete in these designs.

When you use placement new, you shouldn't call delete, but you should call the destructor explicitly.

[Lindley]

Well, placement delete. However, that isn't necessary if the types in question don't allocate resources internally, which may be the case here.

[dude_1967]

Thanks for the further suggestions.

The types I am creating with placement new never delete. They also don't alocate any further resources internally.

It's kind of a funny region --- the world of tiny embedded systems. You turn on your microcontroller, initialize your CPU, stack-pointer, hardware, SRAM, stack, ctors, etc. Then you might make your singleton instances, as run-time progresses, with placement new.

The microcontroller runs and runs and runs until someone mercifully switches it off. main does not return. It's a different kind of design than most people are used to. For this design, I am making a kind of "one-shot" heap.

I've got it all under control now.

Again, thanks for all the help. I always get good answers at codeguru.

Sincerely, Chris.

[JohnW@Wessex]

This article by Dr Dobbs may be of some use or inspiration.

http://www.drdobbs.com/184403759

I used information from here to help design allocators that grabbed space from the stack.

[JohnW@Wessex]

It's kind of a funny region --- the world of tiny embedded systems.

Up until my current job all my work was with embedded systems (6809, 68000). I used to quite enjoy it. There was no OS; If you wanted to print to the screen you had to first write the code that took the output from printf and wrote the pixels to the video memory from your own bitmap font definitions. Ah, those were the days.. (Sits back in chair basking in warm rosey glow of nostalgia )