Kill the buggy 2.6.x compiler

[stocki]

Please bring the 2.7 compiler to 2.8 finally. The 2.6 compiler is horrible.

[Leledumbo]

No compiler is bug free, every version have bugs. What's your problem? I'm using 2.6.2 in my office just fine, it works even for complex apps. This is not the way to bring next version faster, there's no even guarantee that the bugs you're facing is already reported and fixed. Found bugs? Report! That's how you should treat a product if you want it to be better.

[BigChimp]

Exactly. Especially because there may still be 2.6.x releases, please report bugs and get fixes into the fixes_2_6 branch.

Of course, you're free to use FPC trunk. I use it with Laz trunk on Windows and it works nicely now.

[BeniBela]

Please bring the 2.7 compiler to 2.8 finally. The 2.6 compiler is horrible.

Excellent idea!

Of course, you're free to use FPC trunk. I use it with Laz trunk on Windows and it works nicely now.

And then you do an svn update and get a bunch of new bugs

[Timewarp]

I agree! You can't use 2.6.2 for x64 Windows

[marcov]

The next release will probably 2.6.3, there is no schedule (or agreement about what it should contain) for 2.8.x yet.

[jwdietrich]

The next release will probably 2.6.3

I would rather assume that it will be 2.6.4.

[sam707]

Please bring the 2.7 compiler to 2.8 finally. The 2.6 compiler is horrible.

bring the 2.8 ?

and what next....? LOOOL

people will complain about it and the 2.9.1 

Okay, why dont you ask instant for the 4.0 running on ubuntu 17 and windows 11

lmao !

As I say = it is opensource , so ! if u are unhappy with features, REMAKE THEM URSELF !!!

[marcov]

The next release will probably 2.6.3

I would rather assume that it will be 2.6.4.

Yup, to be 2.6.4 release based on the current 2.6.3 codebase, my mistake.   

[stocki]

The next release will probably 2.6.3, there is no schedule (or agreement about what it should contain) for 2.8.x yet.

I don't want the 2.6 branch for further releases. It contains tons of bugs. 2.7 has the fixes and is very stable. Working on 2.6 makes no sense. Killing it now saves a lot of time.

[Bart]

I don't want the 2.6 branch for further releases. It contains tons of bugs. 2.7 has the fixes and is very stable. Working on 2.6 makes no sense. Killing it now saves a lot of time.

Well then, use 2.7.1.
There actually is a release plan for fpc.

Bart

[taazz]

1) I am using 2.6.2 and so far I haven't any problems.
2) other than the 64bit bug that I expect it will be correct on 2.6.4 what other bugs stops you from using the 2.6.x compiler line?

By the way lots of bugs is not an acceptable answer, which ones you need to be corrected?
Personally I would prefer if the 2.7.x remained in development a little longer I had a problem the last time I checked which I would like to report before any release is made.

[Timewarp]

64bit bug that I expect it will be correct on 2.6.4

Where is this clue "SEH fix is planned for 2.6.4"?

I can use 2.7.1, but there will be no open source. Currently I need to apply few custom patches anyway

[taazz]

64bit bug that I expect it will be correct on 2.6.4

Where is this clue "SEH fix is planned for 2.6.4"?

no clue, I said that "I expect it to be included" not that they will included.

I can use 2.7.1, but there will be no open source. Currently I need to apply few custom patches anyway

Errm OK?

[Leledumbo]

I don't want the 2.6 branch for further releases. It contains tons of bugs. 2.7 has the fixes and is very stable. Working on 2.6 makes no sense. Killing it now saves a lot of time.

You're still being unclear (what bugs? have you reported it? has it been fixed? fixed in what version? it all will be written in your bug report), other than (probably fatal, no idea since I'm still on x86) x64 bugs, everything else is mostly fine. 2.7.X is NOT stable, you're maybe lucky to have a perfectly working revision, but a broken revision update can come anytime. You just haven't faced it (I have, and when it happens, with your current attitude, you might stop using FPC at all).

2.7.X is currently the one where developers are free to add new features or fix HUGE bugs, this is not possible for 2.6.X. Some small features might be backported but fixed bugs are the main concern for patch release (the last digit in FPC versioning). 2.6.X has much lower chance for new bugs to appear than 2.7.X. Please understand the development lifecycle of FPC, don't be selfish (and no guarantee 2.8.X would be bug free anyway).

I can use 2.7.1, but there will be no open source. Currently I need to apply few custom patches anyway

Why don't you send the patches instead?