[fpc-pascal] Some features for FPC 3.0?

[Sven Barth]

On 17.02.2015 19:20, silvioprog wrote:
> On Tue, Feb 17, 2015 at 2:49 PM, Sven Barth <pascaldragon at googlemail.com
> <mailto:pascaldragon at googlemail.com>> wrote:
>
>     On 17.02.2015 18:25, silvioprog wrote:
>
>         On Tue, Feb 17, 2015 at 1:41 PM, Sven Barth
>         <pascaldragon at googlemail.com <mailto:pascaldragon at googlemail.com>
>         <mailto:pascaldragon at __googlemail.com
>         <mailto:pascaldragon at googlemail.com>>> wrote:
>
>              Am 17.02.2015 16:29 schrieb "Bee" <bee.ography at gmail.com
>         <mailto:bee.ography at gmail.com>
>              <mailto:bee.ography at gmail.com
>         <mailto:bee.ography at gmail.com>>__>:
>               >
>               > Hi,
>               >
>               > Just got an article about new language features from
>         RO's Oxygene
>              language. I think some of them might be good to be
>         (considered and)
>              implemented in FPC v.3.
>               >
>               > http://blogs.remobjects.com/__blogs/mh/2015/01/28/p7049
>         <http://blogs.remobjects.com/blogs/mh/2015/01/28/p7049>
>               >
>               > What do you think? :)
>               >
>
>              Some features are interesting and are on my own ToDo list (for
>              example tuples). There will however be no roadmap for these
>         features
>              and more importantly they won't be part of 3.0, because
>         that version
>              is currently prepared for release and thus has a feature
>         freeze.
>
>              Regards,
>              Sven
>
>         It would be nice if FPC adopt RC versions. So anyone could do
>         tests just
>         installing it via setup, instead of using GIT / SVN. And Lazarus RCs
>         could be release using this RCs FPCs (e.g: Lazarus-1.4-RC1 has
>         FPC-3.0.0-RC1).
>
>
>     We /are/ doing RCs just like we've done in the past. Before 3.0.0
>     will be released there will at least be a 3.0.0RC1 and maybe also a
>     3.0.0RC2. But it takes time to prepare these and thus RCs are only
>     prepared when a new release is planned. Everything else would be -
>     simply spoken - a waste of our time that is better spent improving
>     the compiler, the RTL and whatever else we have.
>
>     Regards,
>     Sven
>
>
> The problem is that FPC take a lot of time to release new versions. If
> there was a version (RCs) every six months it would help a lot.
>
> Today I'm 32 years old, and probably I'll see the FPC 3.0 be released
> when I'm 33 years old. FPC 4.0 -> 40 years old. FPC 5.0 -> I will
> be already retired. =D

You shouldn't bother with version numbers too much. The next version 
could have as easily been 2.8 and the one after it 2.10. It's the 
features that count... And our normal rythm is a major release around 
every two years (currently a bit longer with 3.0, but nobody's perfect...)

> Just suggestions. I follow other programmer tools, and they don't take
> much time to release new versions, and some of them have fewer
> programmers that FPC community. =/

Regards,
Sven