Recent

Author Topic: InLine Forest (and Gump)  (Read 1077 times)

piGrimm

  • Guest
InLine Forest (and Gump)
« on: January 20, 2018, 09:28:49 pm »
can someone eplain why there is plenty of {$IFDEF xxx_INLINE} in fpc AND lazarus sources???

to check what I am talking about please enter the regular expr

\$ifdef(.*)inline

into laz IDE Search >>> "find in files" tools and search for all sources of laz or fpc

SO!! If I want to build a project with INLINED versions of some units, I MUST check which predefined switches have been choosen by each contributor???

Noone did never plan to UNIFY these switches so I (and we) could compile INLINING OR NOT by using only one (or few) define(s)?
I ask because, I think I waste my time looking for inlines_defines into each unit my projects use
Thank you
« Last Edit: January 20, 2018, 09:30:40 pm by piGrimm »

Thaddy

  • Hero Member
  • *****
  • Posts: 14382
  • Sensorship about opinions does not belong here.
Re: InLine Forest (and Gump)
« Reply #1 on: January 20, 2018, 09:32:06 pm »
Well some of it can be gone but:
- still not every platform can be inlined
- not all combinations of Lazarus and FPC support it.

But basically a lot of it can be removed by now. But hey.... put in some effort... would be appreciated.... 8-)
Object Pascal programmers should get rid of their "component fetish" especially with the non-visuals.

piGrimm

  • Guest
Re: InLine Forest (and Gump)
« Reply #2 on: January 20, 2018, 09:36:51 pm »
(**) of course I do not ask for third part packages, but, as you all understood, for FPC/LAZARUS cores units and packages

 

TinyPortal © 2005-2018