What's the timetable for the next release? Can we assume that all of "trunk" will be in it or will it be more nuanced?
Tony Whyman
MWA

Mailing lists / fpc-pascal / 2016-10
9 messages · 6 people · –
Reply by email Subscribe to this list Your subscription
Read-only archive. Use j and k to move between messages.
What's the timetable for the next release? Can we assume that all of "trunk" will be in it or will it be more nuanced?
Tony Whyman
MWA
"Tony Whyman" wroteWhat's the timetable for the next release? Can we assume that all of
"trunk" will be in it or will it be more nuanced?
The next release will be 3.0.2 (soonish) which will contain quite some fixes compared to 3.0.0, but definitely not everything and most importantly no new compiler and/or language features. That's for the next major release (3.2.0) for which we currently have no timetable (but as a very rough estimate one can say that it's around two years between major releases).
Regards,
Sven
What's the timetable for the next release? Can we assume that all of "trunk" will be in…
In our previous episode, Tony Whyman said:
What's the timetable for the next release?
Should be out 2 months ago. Problems with documentation tool are delaying.
Can we assume that all of "trunk" will be in it or will it be more nuanced?
It is a fixes to 3.0 only, no new language features, and only non intrusive fixes, specially on the compiler side.
The RTL and packages are a bit more state of the art, and a lot has been merged up to about july. (when the RC1 was packaged, though it is still not out).
Due to the extreme long span between rc1 and final release probably a small round of merging of critical stuff will still be done (or rc1 will be skipped, some merging done, and then directly RC2).
"trunk" will be in it or will it be more nuanced? The next release will be 3.0.2…
slow development but it is the best compiler ever ;) i hope i can see fpc 4.0 befor dying :D
2016-10-11 21:59 UTC+02:00, Sven Barth :
code dz wrotei hope i can see fpc 4.0 befor dying
Well, you have the source code. Simply change the version number constant and rebuild it. ;-)
Regards,
Graeme
Graeme Geldenhuys wroteWell, you have the source code. Simply change the version number constant and rebuild it. ;-)
The danger in that is that he might get so excited by the prospect of seeing a 4.0 version of fpc, that he may die of cardiac arrest in the process.
Bart
Bart wroteThe danger in that is that he might get so excited by the prospect of seeing a 4.0 version of fpc, that he may die of cardiac arrest in the process.
Thankfully FPC comes with the following disclaimer. :-p
“
This program is distributed in the hope that it will be useful, but WITHOUT ANY WARRANTY; without even the implied warranty of MERCHANTABILITY or FITNESS FOR A PARTICULAR PURPOSE. ”
Regards,
Graeme
Of course, fpc might skip version 4 altogether. There is precedent. Winamp skipped version 4 with some lame excuse about not wanting to market "Winamp 4" skins ;-)
Thankfully FPC comes with the following disclaimer. :-p “ This program is distributed…
due to the fact that there is no fixed time between major releases , one can wait maybe 10 years to see a next major release , just like gcc4 (2004-2014) , in the other hand gcc5 lives only 1 year .