Board index » cppbuilder » fixing rc bug in bcb6 (hijacked thread)

2007-02-15 07:51:58 AM
cppbuilder23
"Dennis Jones" < XXXX@XXXXX.COM >wrote in message
 

"Duane Hebert" < XXXX@XXXXX.COM >wrote in message
2. For each RC file in your project (they will contain 'CONTAINERID="RC"'),
replace the "RC" with "RCCompiler"
3. Save the modified BPR.
4. Open the project in the IDE -- the IDE will modify the project somehow (I
don't remember off-hand what this change is), and you will see that the
'save' icon is now clickable.
5. Save the (IDE-modified) project.
You're done. Your project will now compile through, incuding all RC files.
However, you must do this whenever you add a new RC file to your project.
If you want to simplify this task a little, you can get my FixBpr utility
(www.grassvalleysoftware.com/FixBpr.zip) which will make the
"RCCompiler" changes for you. Then you just follow steps 4-5 above to let
the IDE complete the fix.
- Dennis
 

"Dennis Jones" < XXXX@XXXXX.COM >wrote in message
think that Borland couldn't issue a fix for this one. Same
thing for the CodeGuard leak in WinHelp or whatever. A
one line change.
That's probably the reason that I even got in this
thread. CodeGear needs to change this.
 

{smallsort}

Duane Hebert wrote:
The fact that there is a workaround shouldn't be a license to ignore a bug.
BDS 2006 works for the most part, but there are an inordinate number of
small problems and minor bugs and failures that make it unpleasant to
use. It a kind of death by a thousand needles, rather than a spear
through the heart.
Many, if not most, of these could be fixed quickly, with no danger of
ABI incompatibility, if there was a real resolve to do so at CodeGear.
The fact that they aren't dealing with these issues effectively tells me
that resolve is not there.
They are trying to create a dichotomy between putting their effort into
bug fixes as opposed to completing a new version, implying they don't
have the resources to do both. And at the same time they say that the
resources they put into developing a new PHP IDE didn't detract from
their BDS efforts in any way. This (and their explicit statements) tells
me they are focused almost completely on new product development and
have no desire to correct bugs in the current product. In fact, I
suspect they intend to drop all maintenance of the current products as
soon as the new CodeGear branded products are released.
Dennis Cote
 

"Dennis Cote" < XXXX@XXXXX.COM >wrote in message
Well, first of all, you need to know there's a workaround. Borland
could have posted this in CG where this was reported in 2002.
The particularly need thing about this bug is that it is easy to miss.
You can change a bunch of code and rebuild a project. It will look
like it succeeded but the exe (or dll) won't be regenerated.
 

Dennis Cote wrote:
 

Randall Parker wrote:
Called "Delphi for PHP" for some strange reason, even though it's not
Delphi as we've traditionally known it.
www.codegear.com/LinkClick.aspx
--
-Brion
There's no such thing as 'one, true way;'
- Mercedes Lackey
 

"Brion L. Webster" < XXXX@XXXXX.COM >wrote in message
C++ Builder to Delphi for C++ ;-)
Db
 

"Db" wrote:
confusion with the language Delphi this will be renamed to Object Pascal. So
the full name of the latest 'Delphi' is actually 'Delphi for Object Pascal
for Win32'. I think.
Somebody know when 'Delphi Studio 2007' will be released?
Peter
 

Peter Agricola wrote:
bet it will be before April 1, 2007 to meet the accounting target of Q1,
2007. Someone will have a boxed copy, or electronic download, of it on
March 31, 2007, at some time zone in the world.
*sheer speculation, so call off the SEC hounds.
--
-Brion
There's no such thing as 'one, true way;'
- Mercedes Lackey
 

Brion L. Webster wrote: