Sign in Join

Live chat for Free Pascal, Lazarus, Delphi and every Pascal programmer.

Mailing lists / fpc-pascal / 2012-01

detect the version of fpc that a feature added to it

4 messages · 4 people · –

Reply by email Subscribe to this list Your subscription

Read-only archive. Use j and k to move between messages.

ik

Hello,

I was looking to understand in what version of FPC ($IF defined ... } was added, and realized that it is not very simple to detect such information. So beside this question of when was it added ?

What is the best way to find such information ?
Another question, should I open a bug for documentation, to add when a specific feature like so was added in the documentation itself ?

Thanks,

Ido

Reply by email

Marco van de Voort
to ik: I was looking to understand in what version of FPC ($IF defined ... } was added, and…

In our previous episode, ik said:

I was looking to understand in what version of FPC ($IF defined ... } was added, and realized that it is not very simple to detect such information.

True. SVN logs of documentation and compiler is the easiest. But that can be exhausting.

But $if is old. Wouldn't be surprised if the 2.x series all supported it.

In general I usually define the oldest version I want to support (now 2.4.4, but from experience 2.4.2 usually works too), and dl and test with that version (and intermediate ones).

Daniel: this is a language feature, the bugreport is about the same problem for libraries.

Reply by email

Graeme Geldenhuys
to ik: I was looking to understand in what version of FPC ($IF defined ... } was added, and…
ik wrote
I was looking to understand in what version of FPC ($IF defined ... } was added, and realized that it is not very simple to detect such information.

If you use a git clone of the FPC repository, you can very easily and quickly (seconds rather than hours) search the commit history and or the patch details (actual code that changed).

eg:

git log -S<text>

That will search the actual changed source code / patch details for <text>.

git log --grep=<text>

That will search the commit message/log for <text>.

Both these commands execute very fast. Indecently, that is how I found in which Lazarus version certain features were implemented (as can be seen in the "New_IDE_features_since" wiki page for Lazarus).

Regards,   - Graeme - _______________________________________________ fpGUI - a cross-platform Free Pascal GUI toolkit http://fpgui.sourceforge.net

Reply by email