On 1/23/16, Graeme Geldenhuys wrote:
>> Q: why "platform"?
>
> Because they don't apply or exist on all platforms. Think OS/2, Haiku
> etc. that use different file systems to the usual linux and Windows ones.
OK.
Better to ask than to file a bugreport;-)
Bart
___
Would it be possible to issue a hint why a procedure can't be inlined at
a specific call?
This could change with the compiler and the user knows what to change
for inlining.
Where do I find documentation/examples on how to define a compiler
intrinsic procedure?
Am 23.01.2016 um 11:53 schrieb Flor
On 2016-01-23 15:02, Bart wrote:
> Q: why "platform"?
Because they don't apply or exist on all platforms. Think OS/2, Haiku
etc. that use different file systems to the usual linux and Windows ones.
Regards,
- Graeme -
--
fpGUI Toolkit - a cross-platform GUI toolkit using Free Pascal
http://f
Am 23.01.2016 um 14:17 schrieb Marc Santhoff:
> On Sa, 2016-01-23 at 11:53 +0100, Florian Klaempfl wrote:
>
>> IMO the only proper solution is to implement delaying as compiler
>> intrinsics as it is done by gcc as well.
>
> Besides using a hardware timer on embedded platforms. Older µC like AVR
Hi,
In revision 32985 faSymlink got a platform modifier.
The same goes for for faHidden.
However these constants are used cross-platform in FindFirst/FindNext.
On *nix faSymlink determines wether or not symlinks are followed in
FF/FN and faHidden is returned for files that start with a period.
Q
On Sa, 2016-01-23 at 11:53 +0100, Florian Klaempfl wrote:
> IMO the only proper solution is to implement delaying as compiler
> intrinsics as it is done by gcc as well.
Besides using a hardware timer on embedded platforms. Older µC like AVR
do not have too much hardware timers, but modern ones no
Am 18.01.2016 um 23:04 schrieb Simon Ameis:
> Thanks for the hint! I've had declared delay_loop_1 and delay_loop_2
> just inside the implementation section.
>
> Maybe these points should be added to documentation for inlining?
I am against documenting this:
- inline is only a hint to the compiler
