Sign in Join

Live chat for Free Pascal, Lazarus, Delphi and every Pascal programmer.

Mailing lists / lazarus / 2003-09

directive NEW1_1

7 messages · 5 people ·

Reply by email Subscribe to this list Your subscription

Read-only archive. Use j and k to move between messages.

Mattias Gaertner
to Mattias Gaertner: On Sat, 13 Sep 2003 10:59:00 +0200 All 1.1 define VER1_1 and not NEW1_1. The declaration…
Show quoted text 12 lines
> > Just a question to clear up something for myself: Does the > > fpc 1.1 on the website define VER1_1? I supose it doesn't, and that it > > defines NEW1_1 instead. Otherwise I see no reason not to change NEW1_1 > > to VER1_1. > > All 1.1 define VER1_1 and not NEW1_1. > The declaration of AssertErrorProc changed. It's longint in 1.0, longint > in the old 1.1 and pointer in the current 1.1. Specify such things as {$ifdef VER1_0} the 1.0.x way {$ELSE} the 1.1.x AND LATER way {$endif}

But then both 1.1 would not compile. The old because of this, and the new because of the expression bug. Or do you mean something like this:

{$ifdef VER1_0}
  // the 1.0.x way
{$ELSE}
  // the 1.1.x AND LATER way
  {$IFDEF New1_1}
    // current, but buggy 1.1
  {$ELSE}
    // old, but working 1.1
  {$ENDIF}
{$endif}
This because of the "AND LATER" part.

It seems this place makes too much trouble and confusion. I will add a comment and try to get a newer 1.1.

Mattias

Reply by email

o2

I compile LCL under FCP 1.1 and I found bug in
utrace.pp
there is
�
�{$IFDEF
NEW1_1}Pointer{$ELSE}Longint{$ENDIF})
�
I don't now why, I must change this
to:
�
�
�{$IFDEF
VER1_1}Pointer{$ELSE}Longint{$ENDIF}); �
�
�
Darek
�

Reply by email

Vincent Snijders
to o2
Show quoted text 18 lines
On Sat, 13 Sep 2003 00:21:29 +0200 "o2" wrote: > I compile LCL under FCP 1.1 and I found bug in utrace.pp > there is > > {$IFDEF NEW1_1}Pointer{$ELSE}Longint{$ENDIF}) > > I don't now why, I must change this to: > > > {$IFDEF VER1_1}Pointer{$ELSE}Longint{$ENDIF}); Show me a working 1.1 and I will change it. The last fpc 1.1, that worked with lazarus, can be found on the website. For the brave, trying the current fpc 1.1, there is the NEW1_1 contruction. Add-dNEW1_1 to the options to compile the LCL.

Just a question to clear up something for myself: Does the fpc 1.1 on the website define VER1_1? I supose it doesn't, and that it defines NEW1_1 instead. Otherwise I see no reason not to change NEW1_1 to VER1_1.

The last time I tried, compiling fpc 1.1 went fine, compiling lazarus (+ everything) failed in synedit, the compiler couldn't parse some booleab expression.

Regards,
Vincent.

Reply by email

Mattias Gaertner
to o2: I compile LCL under FCP 1.1 and I found bug in utrace.pp there is � �{$IFDEF…
Show quoted text 26 lines
On Sat, 13 Sep 2003 09:48:23 +0200 Mattias Gaertner wrote: > On Sat, 13 Sep 2003 00:21:29 +0200 > "o2" wrote: > > > I compile LCL under FCP 1.1 and I found bug in utrace.pp > > there is > > > > {$IFDEF NEW1_1}Pointer{$ELSE}Longint{$ENDIF}) > > > > I don't now why, I must change this to: > > > > > > {$IFDEF VER1_1}Pointer{$ELSE}Longint{$ENDIF}); > > > Show me a working 1.1 and I will change it. > The last fpc 1.1, that worked with lazarus, can be found on the > website. For the brave, trying the current fpc 1.1, there is the > NEW1_1 contruction. Add-dNEW1_1 to the options to compile the LCL. Just a question to clear up something for myself: Does the fpc 1.1 on the website define VER1_1? I supose it doesn't, and that it defines NEW1_1 instead. Otherwise I see no reason not to change NEW1_1 to VER1_1.

All 1.1 define VER1_1 and not NEW1_1.
The declaration of AssertErrorProc changed. It's longint in 1.0, longint in the old 1.1 and pointer in the current 1.1.

The last time I tried, compiling fpc 1.1 went fine, compiling lazarus (+ everything) failed in synedit, the compiler couldn't parse some booleab expression.

Mattias

Reply by email

Marco van de Voort
to Mattias Gaertner
Show quoted text 8 lines
> Just a question to clear up something for myself: Does the > fpc 1.1 on the website define VER1_1? I supose it doesn't, and that it > defines NEW1_1 instead. Otherwise I see no reason not to change NEW1_1 > to VER1_1. All 1.1 define VER1_1 and not NEW1_1. The declaration of AssertErrorProc changed. It's longint in 1.0, longint in the old 1.1 and pointer in the current 1.1.

Specify such things as

  {$ifdef VER1_0} the 1.0.x way {$ELSE} the 1.1.x AND LATER way {$endif}

This because of the "AND LATER" part.

Reply by email

Peter Vreman
to o2: I compile LCL under FCP 1.1 and I found bug in utrace.pp there is � �{$IFDEF…
Show quoted text 17 lines
> > {$IFDEF NEW1_1}Pointer{$ELSE}Longint{$ENDIF}) > > > > I don't now why, I must change this to: > > > > > > {$IFDEF VER1_1}Pointer{$ELSE}Longint{$ENDIF}); > > > Show me a working 1.1 and I will change it. > The last fpc 1.1, that worked with lazarus, can be found on the > website. For the brave, trying the current fpc 1.1, there is the > NEW1_1 contruction. Add-dNEW1_1 to the options to compile the LCL. Just a question to clear up something for myself: Does the fpc 1.1 on the website define VER1_1? I supose it doesn't, and that it defines NEW1_1 instead. Otherwise I see no reason not to change NEW1_1 to VER1_1.

The compiler defines VER1_1

The last time I tried, compiling fpc 1.1 went fine, compiling lazarus (+ everything) failed in synedit, the compiler couldn't parse some booleab expression.

There are currently some major changes in the 1.1 compiler that make it a bit less stable. The major changes are now in place and the compiler will stabilize again in the next weeks. The snapshot building is already working again.

Peter

Reply by email

Mattias Gaertner
to o2: I compile LCL under FCP 1.1 and I found bug in utrace.pp there is � �{$IFDEF…
Show quoted text 9 lines
I compile LCL under FCP 1.1 and I found bug in utrace.pp there is {$IFDEF NEW1_1}Pointer{$ELSE}Longint{$ENDIF}) I don't now why, I must change this to: {$IFDEF VER1_1}Pointer{$ELSE}Longint{$ENDIF});

Show me a working 1.1 and I will change it.
The last fpc 1.1, that worked with lazarus, can be found on the website. For the brave, trying the current fpc 1.1, there is the NEW1_1 contruction. Add -dNEW1_1 to the options to compile the LCL.

Last time I tried the 1.1, I got:

/usr/src/redhat/BUILD/fpc-1.1/compiler/ppc386 -Xs -OG2p3 -n -Sg -Fu/usr/src/redhat/BUILD/fpc-1.1/rtl/linux -di386 -dRELEASE h2pas.pas h2pas.pas(2502,1) Fatal: Internal error 200305301

Mattias

Reply by email