Subj : Re: Multi-Thread and memory allocation error (or bug in 5.02). To : borland.public.cpp.borlandcpp From : "Martin Catney" Date : Tue Sep 02 2003 07:38 pm We did not use Builder 4 with OWL for several reasons but I can not remember why. Not having CodeGuard was one and I think we had probelms with the 16-bit VBX control we were using. Do you know if any one has successfully compile OWL, or OWLNext, with Builder 6? Martin "Ed Mulroy [TeamB]" wrote in message news:3f54c4bb@newsgroups.borland.com... > So, even though you used BCB4 and it came with OWL you never moved to using > OWL in Builder? I think you have painted yourself into a corner. That > situation is not going to go away. It might be time to deal with it. > > . Ed > > > Martin Catney wrote in message > > news:3f5474b3@newsgroups.borland.com... > > > > We cannot move to Builder 6 as alot of our code is based on the OWL > > libraries and re-coding the whole application will take some time, > although > > ultimately we will need to move to another library which may be VCL or > CLX. > > We have been using Builder 4 for years for all new dialogs but we cannot > > move them to Builder 6 without some restructuring/recoding because of the > > difference in the C++ name mangling between Builder 6 and Borland > > 5.02/Builder4. > > So it looks like we are going to have to use Borland C++5.02, Builder 4 > and > > now Builder 6. A bit of a mess in the short term until we restructure the > > code. > > .