[fpc-devel] Inlining problem and LEB128

[J. Gareth Moreton]

Fair enough - thank you for the insight.

To clarify, it is easy enough to demand "inline" appear in the interface 
section, but it breaks a lot of pre-existing code.  I'll have a think 
about how to implement the alternative solution of "implementation-only 
inline" only affecting the routine locally.

Gareth aka. Kit


On 24/06/2019 06:19, Sven Barth via fpc-devel wrote:
> Am 24.06.2019 um 01:02 schrieb J. Gareth Moreton:
>> That's a point, true.  I've been for openness a lot lately, and one 
>> doesn't normally distribute the PPU files with a closed-source 
>> project, but I guess for those programs that need compiling on Linux 
>> before they can be run, it's not very desirable if the PPU files 
>> contain information on, say, a licence key algorithm.
> It's not only projects aka excutables, but also components that can be 
> used with e.g. Lazarus. There *do* exist commercial, closed source 
> component providers that only provide the PPU (and maybe an interface 
> only unit so that Lazarus' code completion works).
>
> Regards,
> Sven
> _______________________________________________
> fpc-devel maillist  -  fpc-devel at lists.freepascal.org
> https://lists.freepascal.org/cgi-bin/mailman/listinfo/fpc-devel
>
>

---
This email has been checked for viruses by Avast antivirus software.
https://www.avast.com/antivirus