TeCanvas in upgrade to BCB6

[dmarlow]

hi

I am trying to compile an application in BCB6 which works properly in BCB4. I get an error message:

"Function cannot return arrays or functions".

The compiler was pointing to the TeCanvas.hpp and the prototype:

"void __fastcall DeleteBitmap(void);" with the error.

does anyone have any ideas or know of any settings that need to be changed to get round this?

cheers

dave

 

[2ffat]

In Borland's community, there was a posting about something similar going from BCB4 to BCB5. I cant find the exact link right now but you might want to search there if you don't get an answer here.
James P. Cottingham

I am the Unknown lead by the Unknowing.
I have done so much with so little
for so long that they think I am now
qualified to do anything with nothing.

 

[2ffat]

This is what I was refering to:
Many Borland-supplied packages change names in different versions of C++Builder. For example, the C++Builder 4 package inet40.bpl is named inet50.bpl in version 5. This causes problems when working on an application created in an earlier version. The workaround is to open the make file and change the names of the packages.

Similarly, some packages are only available in certain editions of C++Builder. For instance, an application that was created in the Enterprise edition might use packages only available in that edition. If the application is then used under a later, but lesser editon of C++Builder (like the Professional edition), packages only available in the higher edition will not be found. In these cases, remove the packages from the make file.


Probably not what you were looking for. James P. Cottingham

I am the Unknown lead by the Unknowing.
I have done so much with so little
for so long that they think I am now
qualified to do anything with nothing.

 

[dmarlow]

Ive seen the old message on the borland group you are referring to but no-one gave an answer to fix the problem.

regarding the second post - I have checked in the makefile and the package names are correct. now im really stuck, any more ideas???

cheers

 

[locutas]

Right above the offending line, include the statement
#undef DeleteBitmap

I can't warrant that no subsequent functions expect to use the previous DeleteBitmap definition, which would get you some nasty subtle errors, but it'll at least compile.

I'll continue to investigate.