Recent

Author Topic: Why Lazarus needs Free Pascal sources?  (Read 3565 times)

geek893

  • New Member
  • *
  • Posts: 24
Why Lazarus needs Free Pascal sources?
« on: June 26, 2016, 12:40:34 pm »
Lazarus says that they are required "for browsing and code completion", but I don't understand what it means.

What functions are unavailable if FP source codes aren't installed?

Bart

  • Hero Member
  • *****
  • Posts: 5290
    • Bart en Mariska's Webstek
Re: Why Lazarus needs Free Pascal sources?
« Reply #1 on: June 26, 2016, 02:48:48 pm »
CodeTools need the fpc source.

Bart

Ñuño_Martínez

  • Hero Member
  • *****
  • Posts: 1186
    • Burdjia
Re: Why Lazarus needs Free Pascal sources?
« Reply #2 on: June 26, 2016, 07:59:54 pm »
What functions are unavailable if FP source codes aren't installed?

Lazarus won't be able to do an in-deep debugging of your code, code completion will not wok at full power, and some other helper functions whould be affected.

Read this for more information about the Lazarus IDE tools.
« Last Edit: June 26, 2016, 08:03:33 pm by Ñuño_Martínez »
Are you interested in game programming? Join the Pascal Game Development community!
Also visit the Game Development Portal

Zoran

  • Hero Member
  • *****
  • Posts: 1831
    • http://wiki.lazarus.freepascal.org/User:Zoran
Re: Why Lazarus needs Free Pascal sources?
« Reply #3 on: June 26, 2016, 08:06:27 pm »
Lazarus says that they are required "for browsing and code completion", but I don't understand what it means.

What functions are unavailable if FP source codes aren't installed?

Code completion will not work means that when you start typing the function name in your code, you will not get the complete function name offered by the source editor. All functions will still work, though.

Graeme

  • Hero Member
  • *****
  • Posts: 1428
    • Graeme on the web
Re: Why Lazarus needs Free Pascal sources?
« Reply #4 on: June 27, 2016, 10:39:02 am »
Code completion will not work means that when you start typing the function name in your code, you will not get the complete function name offered by the source editor.
If that is the case, it can be inaccurate and improved to not require FPC source code. Let me explain.

Inaccurate:
  If it uses the source code to determine function names and properties,
  and you are using FPC Trunk code, but a slightly older FPC Trunk
  binary, the source code could show a function or property, but that
  isn't already in the current FPC Trunk binary.

Not requiring FPC source code:
  CodeTools could be improved to actually read the compiled .PPU files
  directly. FPC already includes a console utility to show how to do this.
  This also means that CodeTools will not have the previous issue
  mentioned. The FPC binary selected and the related .PPU files will
  always match and give a true view of what methods or properties
  are available when you hit Compile.

The other point is that not requiring FPC source code, means you will save a lot of disk space - that could be very important for certain platforms.
« Last Edit: June 27, 2016, 10:40:50 am by Graeme »
--
fpGUI Toolkit - a cross-platform GUI toolkit using Free Pascal
http://fpgui.sourceforge.net/

 

TinyPortal © 2005-2018