[fpc-devel] Breaking change in FPC 2.6.1

Graeme Geldenhuys graemeg.lists at gmail.com
Wed Apr 25 13:17:36 CEST 2012

On 25 April 2012 13:10, Jonas Maebe <jonas.maebe at elis.ugent.be> wrote:
> That's not entirely correct.

Ah yes, the core developers live by different rules to all of use.

> features or important bug fixes that may break backwards compatibility can
> also be merged under certain circumstances.

Strange then that in the last few years of me using FPC released
versions and tracking the "fixes" branch, I can't recall every seeing
a merge that breaks so much code in a "stable release" - yet is
allowed to stay.

Hell, I asked for much less in the past - and that was declined purely
because it was a "minor new feature" - even though it wouldn't break
anybody's code.

  - Graeme -

More information about the fpc-devel mailing list