Board index » delphi » Upgrade of BC++ 4.52 to 32 bit compiler

Upgrade of BC++ 4.52 to 32 bit compiler

Is it possible to upgrade the BC++ 4.52 compiler to a true 32 bit
compiler?  Also which version of the BC++ compiler was a true 32 bit
compiler?  Does Borland offer this one for free?
 

Re:Upgrade of BC++ 4.52 to 32 bit compiler


"Wayne A. King" ha escrito:

Quote
> [...]
> >Also which version of the BC++ compiler was a true 32 bit compiler?

> All from BC++ 5.0 and up had/have a 32-bit IDE. Note that even with
> BC++ 4.52 you have a true 32-bit "compiler" in bcc32.exe.

i'm confused...When compiling using the BC4.52 IDE options (Platform = Win32) is
not a "real" 32 bits compiling?

Sergio

Re:Upgrade of BC++ 4.52 to 32 bit compiler


On Wed, 03 Oct 2001 09:50:26 -0400, "James D. Stewart"

Quote
<JSTEW...@HQ.SATOTRAVEL.COM> wrote:
>Is it possible to upgrade the BC++ 4.52 compiler to a true 32 bit compiler?  

If by "upgrade" you mean some sort of patching, the answer is "no".
If you mean using a valid purchased license for BC++ 4.52 as a
means to a discount when purchasing the latest C++ compiler
offering, the answer is "yes".

Quote
>Also which version of the BC++ compiler was a true 32 bit compiler?

All from BC++ 5.0 and up had/have a 32-bit IDE. Note that even with
BC++ 4.52 you have a true 32-bit "compiler" in bcc32.exe.

Quote
>Does Borland offer this one for free?

No. You can download the latest compiler and related tools
(from the Builder 5 package), but they are *command line tools*
only. (No IDE.) If you have used bcc/bcc32 and tlink/tlink32 from
BC++ 4.52 then you know what I mean. If you *purchase* the full
Builder product, you *may* still be able to get the BC++ 5.02
compiler for free.

--
Wayne A. King
(ba...@torfree.net, wayne.k...@ablelink.org,
 wak...@idirect.com, Wayne_A_K...@compuserve.com)

Re:Upgrade of BC++ 4.52 to 32 bit compiler


Quote
> i'm confused...When compiling using the
> BC4.52 IDE options (Platform = Win32) is
> not a "real" 32 bits compiling?

It does not mean that it is a real 32 bit system.  It means that the BC++
4.52 IDE and therefore the graphical debugging interface is 16 bits so only
Turbo De{*word*81} can be used to debug.  It means that the version 4.52
compiler you are using is six years old.  It means that the libraries and
header files support what Win32 was in 1995, nothing for  Win95 OEMSR2,
nothing for Win98, nothing for WinME, and nothing for Windows 2000.

Borland C++ is not a current product.  The current product is Borland C++
Builder, BCB, the product covered in the newsgroups with the word
'cppbuilder' in their name.

.  Ed

Re:Upgrade of BC++ 4.52 to 32 bit compiler


Thanks for your inmediate answer. Just one more question before i get
completely convinced of switching to BCB, is the basic programming
lenguage/system easy to learn when BC++ is known? I guess all the basis are the
same (classes, events, etc), but with new implementations and (as far as i
know) OWL classes are not used in the same way or not used at all... i know i
should also ask this question in a cppbuilder newsgroup, but the thread is this
one.

"Ed Mulroy (TeamB)" ha escrito:

Quote

> Borland C++ is not a current product.  The current product is Borland C++
> Builder, BCB, the product covered in the newsgroups with the word
> 'cppbuilder' in their name.

> .  Ed

Re:Upgrade of BC++ 4.52 to 32 bit compiler


Before I start, I apologize in advance for all the ackronyms.  (I wrote this
after what is below, after seeing how many letter abbreviations crept in.)

The BCB (Borland C++ Builder) IDE is very different from that of BC++.  It
is based on the Visual Control Library (VCL) instead of OWL.  The IDE has a
lot of things for RAD (Rapid Application Development) and is advertised as a
RAD tool.  Most of the things involve using the VCL.  If you use OWL or are
like me and mostly do Windows API programming, there isn't much RAD for you
in the IDE.  From what I've seen the rest of the world loves the VCL and
finds it easy to learn and use.  While OWL is written in C++, the VCL is
written in whatever language Delphi uses (kind of Pascal, called Object
Pascal but not the Object Pascal that was around before Borland started
using the term).  C++ Classes are written to interface with the Delphi
libraries and you use those classes.

BCB supports the current C++ standard which has evolved quite a bit from the
provisional standard that existed when BC++ was current.  I remember that
when doing a book on BC++ 4 and again on BC++ 4.5 having to fight with the
publisher to get him to let me put something in on templates and he wouldn't
let me do anything at all with exception handling.  Now templates seem to be
involved in nearly everything that is done in C++.  The STL (Standard
Template Library) and exception handling have radically changed how code is
written but also have greatly improved the quality and especially the
freedom from memory allocation related errors.

There are (at least) three versions of Builder, Standard, Professional and
Enterprise.  Standard is the cheapest, made for people who are casual users.
If you are doing anything with it for a living or at least to make money you
should get the Professional version (if you need Enterprise you'll know it).
OWL (and MFC) come on the Professional and above Companion Tools CD but if
you wanted to stay with OWL you probably want to use OWLNext which is a
continuing, public domain, development of OWL to track the latest funnies
that Microsoft puts into Windows.  My preferences lean toward OWL and
therefore to OWLNext, but people really get into the VCL quickly and seem to
like it.

BCB features
  http://www.borland.com/bcppbuilder/companiontools/
  http://www.borland.com/bcppbuilder/productinfo/feamatrix/

OWLNext (web site seems to change or maybe these are mirrors, I have all of
these, and each worked at some time - if one isn't found, try the next link)
  http://members.nbci.com/owlnext/
  http://owlnext.sourceforge.net/
  http://www.geocities.com/SiliconValley/Campus/5642/owlnext.html
  http://owlnext.starbase21.com/

Note that BCB only supports 32 bit programs.  It does not create programs
for DOS or for 16 bit Windows 3.1* so keep your BC++ 4.52 (they used to ship
a BC++ 5.02 CD or in some versions a coupon for one with BCB - I don't know
if they still do that).

BCB has a free version.  The command line tools can be downloaded from here:
  http://www.borland.com/bcppbuilder/freecompiler/

The VCL, IDE, GUI de{*word*81} and other goodies are part of the commercial
product you buy.  They are not part of the download.  Some people have
written up a way to use those command line tools with the BC++ 5.* IDE but
there really isn't much in the BC++ IDE that works well with them and I do
not think of this as anything but a hobbiest solution.  If you're doing it
for a living or even to make a few bucks on the side I do not recommend
going that route.  Others have written their own IDE's.  I have not found
one of them that I can stand.

You would probably get a better answer if you posted your question over on
borland.public.cppbuilder.non-technical where other users can give their
opinon (undoubtedly you'll hear from a couple who have discovered real and
imagined bugs just as you here such things on this group - don't get beat
down from that).

Side Note: Yes, I'm on TeamB, but I don't work for Borland (never have).
The opinions I give are my own.

.  Ed

Re:Upgrade of BC++ 4.52 to 32 bit compiler


Quote
> finds it easy to learn and use.  While OWL is written in C++, the VCL is
> written in whatever language Delphi uses (kind of Pascal, called Object
> Pascal but not the Object Pascal that was around before Borland started
> using the term).  C++ Classes are written to interface with the Delphi
> libraries and you use those classes.

But there are some restrictions to these classes - like the objects can be created
only by dynamic allocation, not on the stack.

Quote

> OWLNext (web site seems to change or maybe these are mirrors, I have all of
> these, and each worked at some time - if one isn't found, try the next link)
>   http://members.nbci.com/owlnext/
>   http://owlnext.sourceforge.net/
>   http://www.geocities.com/SiliconValley/Campus/5642/owlnext.html
>   http://owlnext.starbase21.com/

There is now registered domain name - www.owlnext.org.
It currently points to owlnext.sourceforge.net.

----
Jogy
http://www.jogy.net/
j...@sirma.bg

Other Threads