What is the current version of FPC?

[Thaddy]

I am more worried about not branching 3.2.3 to 3.2.5 after the first RC for 3.2.4. That seems wrong.

[Remy Lebeau]

I think that @Remy is searching for a new stable release of FPC for his Indy project.
I guess he is working on the project to update it and therefore being compatible with both Delphi and Lazarus / FPC he wanted information to test it with "something" recent.

Yes, exactly.  In this particular case, I needed to fix a compiler error in Indy due to FPC's recent signature change of FreeAndNil() to match Delphi. I was looking for a version number that I could test FPC_FULLVERSION against to know which version made that signature change public.  But as the change is just in the trunk and not in a stable release yet, I guess there is no quick way to test that.  But, it's usually not that big a deal for Indy to just assume users are using the latest FPC trunk.

Also, where is FPC_FULLVERSION actually defined? I downloaded the latest FPC source, and I see many references in the code that use it, but I can't find the actual declaration.  I know it is a predefined macro, but where are those created in the source?

I think he is "rewriting" the code with a new version of Indy making important changes, first of all to the SSL features (now in fact delegated to addons external to Indy, even if perfectly integrated), but not only.

I am indeed in the process of making some rewrites to Indy, but they should not really affect FPC, at least as far as the compiler is concerned, since they are more about just removing existing code.

And for this it needs the latest stable release (which it probably thought was newer than 3.2.2).

Indeed, I know FPC is always being worked on, and did expect there to be newer packaged releases than what I already had.

[dsiders]

Also, where is FPC_FULLVERSION actually defined? I downloaded the latest FPC source, and I see many references in the code that use it, but I can't find the actual declaration.  I know it is a predefined macro, but where are those created in the source?

Located in : fpcsrc/compiler/options.pas

Code: [Select]

set_system_macro('FPC_FULLVERSION',Format('%d%.02d%.02d',[StrToInt(version_nr),StrToInt(release_nr),StrToInt(patch_nr)]));

[Remy Lebeau]

Located in : fpcsrc/compiler/options.pas

Thanks. Looks like FPC_FULLVERSION in the main branch is 3.3.1 which has not been rolled since 2018 Wait, how is that possible when 3.2.2 was released in 2021?

[Thaddy]

AFAIK 2018 was just the introduction date of fpc_fullversion. Before 2018 it was also possible to obtain a full version number, but in a more complex way. If it hasn't been touched that means no work

[dbannon]

There are many of us that accept that the current development branch can also be interpreted as a rolling release.

I agree, and use 3.2.4rc myself. But try telling Debian that !

The lack of resources for the release management and the multitude of platforms that must be build are frankly the only things that hold back a new official release.

Then why don't they ask for help ? Ignore questions about what are the problem platforms ?

I am at a loss how this came about, because that is imnho a mistake.

Thaddy, you have made a typo there, Oh, I see .....

Davo

[wp]

Yes, exactly.  In this particular case, I needed to fix a compiler error in Indy due to FPC's recent signature change of FreeAndNil() to match Delphi. I was looking for a version number that I could test FPC_FULLVERSION against to know which version made that signature change public.  But as the change is just in the trunk and not in a stable release yet, I guess there is no quick way to test that.

To check against FPC trunk version I usually have:

Code: Pascal  [Select][+][-]

1. {$IF FPC_FullVersion >= 30301}
2.   code_for_fpc331;
3. {$ELSE}
4.   code_for_fpc322_or_324_or_oder;
5. {$IFEND}

[Remy Lebeau]

AFAIK 2018 was just the introduction date of fpc_fullversion. Before 2018 it was also possible to obtain a full version number, but in a more complex way. If it hasn't been touched that means no work

Maybe I didn't make myself clear.  I'm not looking at compiler/options.pas now, I'm looking at compiler/version.pas instead, which defines the actual constants which make up the components of FPC_FULLVERSION. According to its history, the constants were set to 3.1.1 in 2015 and then set to 3.3.1 in 2018, and have been that way since.  At no point were the constants ever set to 3.2.2, that I can see.  How is that possible if 3.2.2 is the current version?

[Remy Lebeau]

To check against FPC trunk version I usually have:

Code: Pascal  [Select][+][-]

1. {$IF FPC_FullVersion >= 30301}
2.   code_for_fpc331;
3. {$ELSE}
4.   code_for_fpc322_or_324_or_oder;
5. {$IFEND}

That would be fine if 3.3.1 were a stable release, but from what I've seen so far, FCP_FULLVERSION has been at 3.3.1 for a long time, and the change I'm interested in right now is recent, so that check won't cover all of the earlier 3.3.1 builds before the change.  But, I suspect this is about as good as I can hope for at the moment.

[marcov]

Maybe I didn't make myself clear.  I'm not looking at compiler/options.pas now, I'm looking at compiler/version.pas instead, which defines the actual constants which make up the components of FPC_FULLVERSION. According to its history, the constants were set to 3.1.1 in 2015 and then set to 3.3.1 in 2018, and have been that way since.  At no point were the constants ever set to 3.2.2, that I can see.  How is that possible if 3.2.2 is the current version?

See the FAQ https://www.freepascal.org/faq.html#versions  Note that releases are on a difference branch than main development, so this is perfectly normal.

Development versions like 3.3.1 are daily versions, without any long term support. So after a few weeks everybody is expected to have updated.

[Thaddy]

@Marco that basically confirms my suspicion that  the fixes branch was not moved after the RC.
We both know that is....unfortunate... (any kind of childish Unicode art added)

I respect the team, you know that.

[Remy Lebeau]

See the FAQ https://www.freepascal.org/faq.html#versions  Note that releases are on a difference branch than main development, so this is perfectly normal.

Wonderful. Thanks.