On Oct 17, 2010, at 2:07 PM, Kyle Sluder wrote:
> On Sun, Oct 17, 2010 at 1:29 PM, Velocityboy wrote:
>> This is actually not always true. If you have an non-static inline in a
>> header file, the compiler is pretty smart about it. You can see this in
>> action if you generate the assembly and
On Sun, Oct 17, 2010 at 1:29 PM, Velocityboy wrote:
> This is actually not always true. If you have an non-static inline in a
> header file, the compiler is pretty smart about it. You can see this in
> action if you generate the assembly and look it it. This:
IIRC there's no guarantee that a tw
On Oct 17, 2010, at 12:05 PM, Kyle Sluder wrote:
> On Oct 16, 2010, at 8:31 PM, Ken Tozier wrote:
>
>> Hi
>>
>> I want to create some inline functions that are universally available within
>> my app, but can't seem to get them working. If I define a set of inlines
>> within a specific class,
On Oct 17, 2010, at 12:05 PM, Kyle Sluder wrote:
> On Oct 16, 2010, at 8:31 PM, Ken Tozier wrote:
>>
>> I want to create some inline functions that are universally available within
>> my app, but can't seem to get them working. If I define a set of inlines
>> within a specific class, they compi
On Oct 17, 2010, at 3:05 PM, Kyle Sluder wrote:
> Think about this for a second: "static" means file scope, so obviously you
> can't reference the symbol from another file. And non-static inlines can't
> actually be inlined because they may be called from elsewhere or have their
> addresses ta
On Oct 16, 2010, at 8:31 PM, Ken Tozier wrote:
> Hi
>
> I want to create some inline functions that are universally available within
> my app, but can't seem to get them working. If I define a set of inlines
> within a specific class, they compile, but If I take the same functions and
> move
