|
| Re: bcc55 static, inline |
 |
Fri, 20 Jul 2007 08:28:04 -040 |
static and inline are C++ keywords. There are no alternate names for them.
What you are using is the set of command line tools from C++ Builder version
5.
Updated help files for BCB 5 are posted here:
http://info.borland.com/techpubs/bcppbuilder/v5/updates/pro.html
Links to tutorials and other sites dealing with the C and C++ languages can
be found here:
http://www.mulroy.org/programg.htm
. Ed
> david wrote in message
> news:46a06d11@newsgroups.borland.com...
>
> Is there any equivilant to the keywords 'static' and 'inline' for Borland
> C builder 5.5?
>
> Unfortunately, my copy of BCB5LANG.HLP seems to be corrupt, so I'm working
> in the dark here.
|
| Post Reply
|
| bcc55 static, inline |
 |
Fri, 20 Jul 2007 18:06:42 +100 |
Is there any equivilant to the keywords 'static' and 'inline' for
Borland C builder 5.5?
Unfortunately, my copy of BCB5LANG.HLP seems to be corrupt, so I'm
working in the dark here.
|
| Post Reply
|
| Re: bcc55 static, inline |
 |
Mon, 23 Jul 2007 09:07:13 -040 |
The two keywords static and inline are not compatible when applied to a
standalone function, a function not part of a class or structure.
static means that a copy of the function exists but its name is not placed
on the public name list so it is not visible to anything in other source
files.
inline means that the function does not exist. In each place where a call
to that function is encountered in source code the compiler inserts machine
code to do its task.
Note that when compiled in debug mode, the option to not inline functions
identified with the inline keyword is normally enabled. This is necessary
in debug mode so that there is an address for the function so you can step
through it when debugging.
. Ed
> david wrote in message
> news:46a426c0@newsgroups.borland.com...
>
> hmmm. I think that my problem is that BCB 5.5
> doesn't seem to accept BOTH 'static' and 'inline'
> on the same function.
>
> I realise that my problem is that I am trying to
> merge code from 2007 with code from 1997 using a
> mixture of tools from 1997-2007.
>
> Got the help file replacement, thanks.
|
| Post Reply
|
| Re: bcc55 static, inline |
 |
Mon, 23 Jul 2007 13:55:47 +100 |
hmmm. I think that my problem is that BCB 5.5
doesn't seem to accept BOTH 'static' and 'inline'
on the same function.
I realise that my problem is that I am trying to
merge code from 2007 with code from 1997 using a
mixture of tools from 1997-2007.
Got the help file replacement, thanks.
(david)
as
Ed Mulroy [TeamB] wrote:
> static and inline are C++ keywords. There are no alternate names for
them.
>
> What you are using is the set of command line tools from C++ Builder
version
> 5.
>
> Updated help files for BCB 5 are posted here:
> http://info.borland.com/techpubs/bcppbuilder/v5/updates/pro.html
>
> Links to tutorials and other sites dealing with the C and C++ languages can
> be found here:
> http://www.mulroy.org/programg.htm
>
> . Ed
>
>> david wrote in message
>> news:46a06d11@newsgroups.borland.com...
>>
>> Is there any equivilant to the keywords 'static' and 'inline' for
Borland
>> C builder 5.5?
>>
>> Unfortunately, my copy of BCB5LANG.HLP seems to be corrupt, so I'm
working
>> in the dark here.
>
|
| Post Reply
|
| Re: bcc55 static, inline |
 |
Mon, 30 Jul 2007 17:14:03 +100 |
I'm working with cross-platform code.
In the environment this particular code was ported
from, static and inline are orthogonal properties.
Inline specifies the behaviour inside the source file:
static specifies the visibility outside the source file.
(david)
Ed Mulroy [TeamB] wrote:
> The two keywords static and inline are not compatible when applied to a
> standalone function, a function not part of a class or structure.
>
> static means that a copy of the function exists but its name is not placed
> on the public name list so it is not visible to anything in other source
> files.
>
> inline means that the function does not exist. In each place where a call
> to that function is encountered in source code the compiler inserts machine
> code to do its task.
>
> Note that when compiled in debug mode, the option to not inline functions
> identified with the inline keyword is normally enabled. This is necessary
> in debug mode so that there is an address for the function so you can step
> through it when debugging.
>
> . Ed
>
>> david wrote in message
>> news:46a426c0@newsgroups.borland.com...
>>
>> hmmm. I think that my problem is that BCB 5.5
>> doesn't seem to accept BOTH 'static' and 'inline'
>> on the same function.
>>
>> I realise that my problem is that I am trying to
>> merge code from 2007 with code from 1997 using a
>> mixture of tools from 1997-2007.
>>
>> Got the help file replacement, thanks.
>
|
| Post Reply
|
|
|
|
|
|
|
|
|
|