VCL classes are derived from TPersistent class - providing means of serializing objects. Probably not exactly the same thing as in VC++, but should be appropriate.
You can not delete .exe file if that app is running, because Windows is using Memory-mapped files when executing apps, which means that .exe file is always open and never copied into RAM completly.
>>What is the difference between C++ and C++ Builder?
USE C++ BUILDER!
You'll make your life easier when working on Win app. C++ Builder is a C++ compiler like any other, but with some language extensions to enable RAD. Essentially, it looks and works just like Delphi, but you write your code...
Huh, first thing that comes to my mind, try Borland's TurboVision. It has all the GUI elements you'll need and is object-oriented (almost ;)
I don't know where to get it now, but it was shipped along with BorlandC++ V3.1 as far as I remember...
Everything is just fine with precompiled-headers! :) And it speeds-up compiling significatnly!
All you have to do is to :
- include system header files above #pragma hdrstop
- include your header files (frequently changed) below #pragma hdrstop
and it should be fine!
If I undestood your problem correctly, there should be no problem if data layout in memory is correct. For example :
BYTE bFloatData[4];
float fValue = *((float *)bFloatData);
As for books : check Amazon. Very good DX9 books have been released recently. Don't worry about MSC++ - oriented coverage, it is the same thing as in BC++, you won't have any problems reading them
Two sugestions :
1. While loading, store numbers in sorted array (or list) and use binary-search to find duplicates. It will reduce time significantly.
or
2. If the range is not too high, use a separate bit-string structure for fast lookup
DevC++ is not RAD tool. So, you can do two things : write pure WinAPI apps, or download and use some of GUI libraries. Check the Google, there are loads of them (FLTK comes to mind...)
Essentialy, the size shouldn't matter, since app was crashing inside Borlandmm.dll! That's just unacceptable! Memory manager must allocate me one byte if I ask for!
But anyway, I got around the problem by overriding global new/delete operator and using LocalAlloc() inside it. It works just fine...
Hello,
I have a very strange crash in BCB. My app is allocating big number of small objects (using 'new'), but suddenly, it started crashing in Borlandmm.dll!
Surely, there is a plenty of memory, and, anyway, it shouldn't crash, but it does and I can't do anything about it!
Does anyone know of...
How about using old BorlandC++ as a compiler by making your project of "MAKE" type, and in your .make file override MS compiler and use old Borland stuff?
Just a guess, haven't tried it, but some other APIs (like Mophun) are using the same approach - separate compiler/linker through...
For Windows, BloodShed Dev-C++ is pretty good one! Full IDE + compiler. And it's free...
Btw, it says "C++", but every C++ compiler can compile pure-C code.
Try to do this : if all of the code for template classes is not already in the class itself, instead of writing template code in .cpp file, put it in e.g. ".inl" file (inline). Then at the end of your template-header file put #inlude "Array.inl". Do it for every header file...
You need to retrieve Windows version. In Builder, it's a global "int Win32Platform" variable.
If it's VER_PLATFORM_WIN32_NT, than it's an NT derivative, usually 2000/XP nowadays.
For more detailed info look at the Win32API help on this subject.
This site uses cookies to help personalise content, tailor your experience and to keep you logged in if you register.
By continuing to use this site, you are consenting to our use of cookies.