Am 06.04.2015 um 19:23 schrieb Michael Ring:
> Thanks,
>
> So do you think it is worth to extend documentation for inline? Or perhaps
> the compiler could give a
> warning when code is not suitable for inlining or is this decision done when
> a caller requests
> inlining and not when the inline
Thanks,
So do you think it is worth to extend documentation for inline? Or
perhaps the compiler could give a warning when code is not suitable for
inlining or is this decision done when a caller requests inlining and
not when the inline function gets compiled?
Michael
Am 06.04.15 um 18:59 s
Am 06.04.2015 um 17:53 schrieb Michael Ring:
> Take the following unit, my goal is to have the code called in the unit
> inlined in the main code.
>
> This works fine when
>
> type
> pLongWord = ^LongWord;
>
> is defined in the interface of the unit.
>
> if this is defined in Implementation t
Take the following unit, my goal is to have the code called in the unit
inlined in the main code.
This works fine when
type
pLongWord = ^LongWord;
is defined in the interface of the unit.
if this is defined in Implementation then Inlining of the code does not
work.
Is this correct behavi
I'll create a branch and commit the supplied patches so far, we can use
this branch to bring things into a reasonable shape.
___
fpc-devel maillist - fpc-devel@lists.freepascal.org
http://lists.freepascal.org/cgi-bin/mailman/listinfo/fpc-devel
