Jonas Maebe wrote:
Yes, but it still contains several known bugs such as cryptic error
messages, context sensitivity (if procedure Foo is declared in units A
and B, and the unit declaring the generic which calls Foo uses A while a
unit declaring a specialisation uses B, then the specialisation
On 27 mrt 2007, at 11:05, Micha Nelissen wrote:
Jonas Maebe wrote:
Yes, but it still contains several known bugs such as cryptic
error messages, context sensitivity (if procedure Foo is declared
in units A and B, and the unit declaring the generic which calls
Foo uses A while a unit decla
Jonas Maebe wrote:
Yes, but it still contains several known bugs such as cryptic error
messages, context sensitivity (if procedure Foo is declared in units A
and B, and the unit declaring the generic which calls Foo uses A while a
unit declaring a specialisation uses B, then the specialisation
On 27 mrt 2007, at 10:37, Bram Kuijvenhoven wrote:
Anyway, I'm looking forward to beta/stable versions from the 2.2.x
branch, and in particular generics support, which will be enabled
in 2.2.x I presume?
Yes, but it still contains several known bugs such as cryptic error
messages, contex
Graeme Geldenhuys wrote:
> What is the version number of /trunk now? 2.2.1? 2.1.4?
2.3.1
Not 2.2.1? ;-) I guess that's to many even numbers to justify a
unstable release.
2.2.1 is the version number of the fixes_2_2 branch between the 2.2.0 and 2.2.2
releases :)
Anyway, I'm looking f
Op Tue, 27 Mar 2007, schreef Graeme Geldenhuys:
> > 2.3.1
>
> Not 2.2.1? ;-) I guess that's to many even numbers to justify a
> unstable release.
When 2.2 is out, the fixes_2_2 branch will be named 2.2.1. Trunk will
ultimately become FPC 2.4.
Daniël_
On 3/27/07, Jonas Maebe <[EMAIL PROTECTED]> wrote:
Even version numbers are reserved for releases (either internal/
external releases), i.e. they correspond to a single source tree
which is tagged. 2.1.2 has been tagged already for internal release
building testing. 2.1.4 will be the first publi
Graeme Geldenhuys wrote:
Hi,
> I am a bit confused with the FPC version numbers in SubVersion.
> Obviously I just don't know or understand how the version numbers in
> FPC work. I do know even numbers are stable and odd numbers unstable.
> The version increments is still a mystery.
;-) Actually
On 27 mrt 2007, at 09:44, Graeme Geldenhuys wrote:
Why has the /Fixes_2_2 branch got a version number 2.1.3? The name is
very misleading. Why not 2.1.2 or 2.2.0?
Even version numbers are reserved for releases (either internal/
external releases), i.e. they correspond to a single source tree
