Comments by Rock Bottom

Rock Bottom 14-Feb-11 14:49pm View

Yeah, I was just thinking whether or not that would be a valid way to solve this, provided we can guarantee only one instance of that class. I'm was just throwing it out there as we suspect that the initialization of static variables on the load of a DLL is the culprit. Also, it's always good to clean up the code and remove any stuff that doesn't make sense (such as all these statics).

Rock Bottom 14-Feb-11 14:18pm View

So, would the same problem still happen with instance variables? I'm just trying to understand where the root of the problem is.

Rock Bottom 14-Feb-11 14:16pm View

Dynamically.

So, would the same problem still happen with instance variables? I'm just trying to understand where the root of the problem is.

Rock Bottom 11-Feb-11 17:19pm View

At this point, the app compiles and links, it's just that sometimes the objects or points get reset across the different scopes. A lot of the code that were statics probably shouldn't stay as statics, that's what I meant when I said they were abused.

I guess I'm just trying to understand what caused the problem so that I can start figuring out how to solve them.

Rock Bottom 11-Feb-11 16:51pm View

Yeah, this is indeed legacy code from many years ago written by someone else. This is in Windows using Visual Studio 2008.

The main thing right now is just that, after we init an instance, next time we come back around, it becomes NULL again. We're suspecting it might have to do with the loading of different DLLs.

Rock Bottom 25-Jan-11 17:33pm View

Any advices on the mounds of LNK2001s that I'm getting?

Rock Bottom 25-Jan-11 15:34pm View

Hi Espen,
The tool seems like it might be a little new for our old application (Borland OWLNext old). Your help is still appreciated though.
Thanks!

Rock Bottom 20-Jan-11 13:52pm View

Doxygen is a great tool, thanks for the recommendation!

Rock Bottom 20-Jan-11 11:35am View

Thanks for the quick response that was one approach that I've considered earlier, but we ultimately decided if we were to do something of this scale, we might as well do it right. The idea is to completely merge it in wherever possible as the 2 applications do share similarities in many places. The separation of the classes weren't very clear back when the application was first written, and a lot of the logic is intertwined. This is not a problem when everything was together with everything else, but it's probably going to be a huge problem now when we try to part things out.

Comments by Rock Bottom (Top 9 by date)