dhjdhjdhj

I was building/testing a simple external where I was using a C++ class for convenience. An instance of the class was created with "new" and stored in the t_object structure.

I found that my environment started crashing occasionally, sometimes when loading another patcher, sometimes (but not always) when unlocking a patcher for editing.

On a whim, I got rid of the dynamic allocation and just made the C++ object live on the stack. All crashes went away.

So I'm wondering if there are some issues around mixing the memory allocators and so forth.

I was building/testing a simple external where I was using a C++ class for convenience. An instance of the class was created with "new" and stored in the t_object structure.
I found that my environment started crashing occasionally, sometimes when loading another patcher, sometimes (but not always) when unlocking a patcher for editing.

are-there-any-issues-when-mixing-c-and-c-or-objective-c-in-an-external

In principle you should be able to use different memory allocation protocols as long as you rigorously stick to the cardinal rule: deallocate with the same protocol that you allocated with.

Disregarding that rule is, of course, the path to perdition.

I can't think of a reason why you should be having the problem you recount. I've had mixed C++ and C allocation schemes in projects in the past (as well as mixing getbytes(), C, and Classic Mac OS allocation--which once upon a time I did quite a bit of). It may have been something other than the actual mixing of allocation protocols, but without seeing the code one can but guess (and I'm afraid I can't take the time to look at more than maybe a dozen lines of code). So all I can say is, if you've got something working stably, then stick with it. And if you've got time to go poking around with a debugger, you might find a way to go back to your mixed memory model, which by rights ought to work. I think.

It may be that I'm stepping on something that is harmless on the stack but blowing up on the heap, but it's a very simple external.

I had checked the Cycling74 includes to ensure they were wrapped inside "extern C++" which they are.

Must be something in my code but it was worth checking to ensure there were no "known" gotchas as I've seen something similar with another external that mixes C and C++.

It may be that I'm stepping on something that is harmless on the stack but blowing up on the heap, but it's a very simple external.
I had checked the Cycling74 includes to ensure they were wrapped inside "extern C++" which they are.

Are there any issues when mixing C and C++ (or Objective-C) in an external?