how do I update my BC++ 5.02 #include files & import libraries?

Thread View: comp.os.ms-windows.programmer.tools

3 messages

[T] Back to Threads [V] Tree View [G] Group Articles

3 total messages Started by John A. Grant Sun, 06 Aug 2000 00:00

#977

Author: John A. Grant
Date: Sun, 06 Aug 2000 00:00

55 lines
3331 bytes

Currently, I have BC++ 5.02, which I think was the last BC++
before "Builder" right?

I'm running into problems using it without the latest import
libraries and #include files, especially for things like
comctl32.dll, which seems to gain new features every month.

I got a copy of the latest commctrl.h file from someone with
VC++, but it's a completely different file from the one supplied
by Borland. It has lots of MS-specific stuff in it and none of the
BC++ specific stuff.  I cut/pasted in a few of the LVS_EX_
#defines, but there's lots of other stuff I'm afraid to touch.

When I use LVS_EX_CHECKBOXES in my .rc file, the RC
can't find that value, even though it's in the commctrl.h file now.
I figured the PCH or other files contained the old commctrl.h files,
so I exited, purged all of the weird BC++ files from the project
directory and did a complete rebuild. Same error. I ended up
adding this in my .rc:
    #ifndef LVS_EX_CHECKBOXES
        #include "commctrl.h"
    #endif
something I've never had to do, because Borland's RC never
required any #include of standard files. Anyway, that compiles
ok.  But when I run the application, there is no image state
list on the side of the listview control.  But I do have version
5.x of comctl32.dll on my system.  I think the style isn't being
recognized because I'm using InitCommonControls() instead
of InitCommonControlsEx()

But I don't have InitCommonControlsEx() in my commctrl.h. I
can paste it in from the VC++ file, but  I will still need to use
IMPLIB to get a new import library. But now I'm getting confused
because I don't really know what I need to do to get this
to work.

So what's the prognosis for BC++ 5.02?  All I want is a good
Win32 API C++ development system - I don't want Delphi,
Builder, OWL or VCL or any of that stuff. Just the straight Win32
API. I've been led to believe that Builder isn't a complete a
development system as BC++ 5.02, so I've stayed with BC++
5.02

I really don't want to move to VC++, because I really do like
BC++  (I've been a loyal fan since TC 1.0). But unless there's
some way to keep updating my #include files to keep pace
with all of this new stuff, I may have to go to the Dark Side and
switch to VC++. Say it ain't so.

Thanks for any tips/help/suggestions/commiseration.

--
John A. Grant  * I speak only for myself *  (remove 'z' to reply)
Radiation Geophysics, Geological Survey of Canada, Ottawa
If you followup, please do NOT e-mail me a copy: I will read it here

Re: how do I update my BC++ 5.02 #include files & import libraries?

#978

Author: Ian Knowles
Date: Mon, 07 Aug 2000 00:00

31 lines
2222 bytes

"John A. Grant" <jazrant@zsc.nrcan.zc.ca> wrote:

>So what's the prognosis for BC++ 5.02?  All I want is a good
>Win32 API C++ development system - I don't want Delphi,
>Builder, OWL or VCL or any of that stuff. Just the straight Win32
>API. I've been led to believe that Builder isn't a complete a
>development system as BC++ 5.02, so I've stayed with BC++
>5.02

IMHO the only sensible thing to do with BC++ 5.02 is to leave it
behind ASAP. Not only will you continue to have issues with such API
headers but if you try to write *standard* C++ you'll end up being
very unhappy indeed.

I have also found the 5.02 compiler to be quite buggy (e.g. I can all
too easily produce code that upon throwing an exception will attempt
to execute a destructor for a local object [especially a string
object] that [due to the execution path] had never actually been
constructed [result == GPF]).

I think that C++ Builder [version 4 patch 2 at least] is a reliable
and (quite reasonably) standard conforming compiler. If you're worried
about RC file editing then you might wish to continue to use 5.02
simply for the resource files (I have actually got used to editing RC
files as text after getting sick of the 5.02 resource editor ripping
out important comments and conditional pre-processor macros :).

Regards,

Ian Knowles (remove the .nospam to reply)

Re: how do I update my BC++ 5.02 #include files & import libraries?

#979

Author: John A. Grant
Date: Mon, 07 Aug 2000 00:00

56 lines
3728 bytes

"Ian Knowles" <ian@who.net.nospam> wrote in message
news:Lfxj5.74643$N4.1973768@ozemail.com.au...
> "John A. Grant" <jazrant@zsc.nrcan.zc.ca> wrote:
>
> >So what's the prognosis for BC++ 5.02?  All I want is a good
> >Win32 API C++ development system - I don't want Delphi,
> >Builder, OWL or VCL or any of that stuff. Just the straight Win32
> >API. I've been led to believe that Builder isn't a complete a
> >development system as BC++ 5.02, so I've stayed with BC++
> >5.02
>
> IMHO the only sensible thing to do with BC++ 5.02 is to leave it
> behind ASAP. Not only will you continue to have issues with such API
> headers but if you try to write *standard* C++ you'll end up being
> very unhappy indeed.
>
> I have also found the 5.02 compiler to be quite buggy (e.g. I can all
> too easily produce code that upon throwing an exception will attempt
> to execute a destructor for a local object [especially a string
> object] that [due to the execution path] had never actually been
> constructed [result == GPF]).
>
> I think that C++ Builder [version 4 patch 2 at least] is a reliable
> and (quite reasonably) standard conforming compiler. If you're worried
> about RC file editing then you might wish to continue to use 5.02
> simply for the resource files (I have actually got used to editing RC
> files as text after getting sick of the 5.02 resource editor ripping
> out important comments and conditional pre-processor macros :).

    Thanks for the comments. I received a pointer to a site
    where I can get a new <commtrl.h>, but there doesn't
    seem to be any ongoing update of this stuff from Borland.
    I hate to admit it, but I think you're right and I may have to
    abandon ship and go with VC++.  The SDK seems to be
    updated almost daily and it always has the latest stuff.
    Unfortunately, most of the #Include files are VC++-specific.
    Well, not really - it's just that they don't accomodate BC++.
    One of the issues is the #pragmas. Luckily, both VC++
    and BC++ use things like pshpack*.h, which helps. BC++
    has support for both Win16 & Win32 and uses /include/win16
    and /include/win32 to keep this stuff separate. That
    immediately causes a problem with the #include files because
    VC++ is Win32-only.

    I have not had any problems with the BC++ IDE or with the
    code that's generated. But I don't use OWL and my C++
    is pretty rudimentary - nothing exotic.

    I'm not sure what you mean by your comment about having
    problems writing standard C. Maybe I don't use enough
    exotic (too me) C++ language features to notice the problem.

--
John A. Grant  * I speak only for myself *  (remove 'z' to reply)
Radiation Geophysics, Geological Survey of Canada, Ottawa
If you followup, please do NOT e-mail me a copy: I will read it here

Thread Navigation

This is a paginated view of messages in the thread with full content displayed inline.

Messages are displayed in chronological order, with the original post highlighted in green.

Use pagination controls to navigate through all messages in large threads.

Back to All Threads