Sign in Join

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

Mailing lists / lazarus / 2003-11

Problems parsing 1.9 source

6 messages · 3 people ·

Reply by email Subscribe to this list Your subscription

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

Mattias Gaertner
to Vincent Snijders: I noticed the lazarus codetools have some problems finding declarations when using fpc…
Show quoted text 10 lines
Hi, I noticed the lazarus codetools have some problems finding declarations when using fpc 1.9 compiler and sources. 1. oldfpccall is not recognized. For example on line 37 of .../fpc/rtl/linux/i386/syscallh.inc: function Do_SysCall(sysnr:TSysParam):TSysResult; {$ifndef VER1_0} oldfpccall; {$endif} oldfpccall is not recognized and parsing stops.

fixed

Show quoted text 10 lines
2. wrong signal.inc included On line 29 of .../fpc/rtl/unix/unix.pp signal.inc is included. This is in the interface section of unix.pp. Lazarus thinks it should include .../fpc/rtl/linux/i386/signal.inc. This is not possible because this file also has some procedure implementation around line 137(which can't be a part of a unit's interface). Apparently the right file to include is .../fpc/rtl/linux/signal.inc. As far as I could see, .../fpc/rtl/linux/i386/signal.inc is not used and might be obsolete. To work around this bug I delete the 'obsolete' file and restart lazarus. Of course after updating fpc from cvs, it is right back.

fixed

Show quoted text 5 lines
3. can't find include file "sysutilh.inc" On line 28 of .../fpc/rtl/unix/sysutils.pp sysutilh.inc is included. Lazarus can't find it because it is in a include directory specially for sysutils: .../fpc/rtl/objpas/sysutils. This include path is only used for sysutils.pp.

fixed

Mattias

Reply by email

Florian Klaempfl
to Vincent Snijders: I noticed the lazarus codetools have some problems finding declarations when using fpc…
Mattias Gaertner wrote 8 lines
>1. oldfpccall is not recognized. >For example on line 37 of .../fpc/rtl/linux/i386/syscallh.inc: >function Do_SysCall(sysnr:TSysParam):TSysResult; {$ifndef VER1_0} >oldfpccall; {$endif} >oldfpccall is not recognized and parsing stops. ts ts. I thought, introducing new keywords is only a Borland illness.

It's not a keyword, it's a modifier ;) Anyways, there is another new one: softfloat; though it applies only to non-i386 architectures :)

Reply by email

Florian Klaempfl
to Vincent Snijders: I noticed the lazarus codetools have some problems finding declarations when using fpc…
Mattias Gaertner wrote 21 lines
On Sat, 08 Nov 2003 00:34:10 +0100 Florian Klaempfl wrote: >Mattias Gaertner wrote: > >>>1. oldfpccall is not recognized. >>>For example on line 37 of .../fpc/rtl/linux/i386/syscallh.inc: >>>function Do_SysCall(sysnr:TSysParam):TSysResult; {$ifndef VER1_0} >>>oldfpccall; {$endif} >>>oldfpccall is not recognized and parsing stops. >> >> >>ts ts. I thought, introducing new keywords is only a Borland illness. > >It's not a keyword, it's a modifier ;) Anyways, there is another new >one: softfloat; though it applies only to non-i386 architectures :) ok. What is a softfloat?

Passing float parameters in integer registers instead the fpu registers, only supported for cpu architectures like the arm where a missing fpu is likely.

Reply by email

Mattias Gaertner
to Vincent Snijders: I noticed the lazarus codetools have some problems finding declarations when using fpc…

On Fri, 7 Nov 2003 19:54:25 +0100
Vincent Snijders wrote:

I'm currently fixing the rpm scripts for 1.9. As soon as I got them, I will fix the paths.

Mattias

Show quoted text 8 lines
I noticed the lazarus codetools have some problems finding declarations when using fpc 1.9 compiler and sources. 1. oldfpccall is not recognized. For example on line 37 of .../fpc/rtl/linux/i386/syscallh.inc: function Do_SysCall(sysnr:TSysParam):TSysResult; {$ifndef VER1_0} oldfpccall; {$endif} oldfpccall is not recognized and parsing stops.

ts ts. I thought, introducing new keywords is only a Borland illness.

Show quoted text 10 lines
2. wrong signal.inc included On line 29 of .../fpc/rtl/unix/unix.pp signal.inc is included. This is in the interface section of unix.pp. Lazarus thinks it should include .../fpc/rtl/linux/i386/signal.inc. This is not possible because this file also has some procedure implementation around line 137(which can't be a part of a unit's interface). Apparently the right file to include is .../fpc/rtl/linux/signal.inc. As far as I could see, .../fpc/rtl/linux/i386/signal.inc is not used and might be obsolete. To work around this bug I delete the 'obsolete' file and restart lazarus. Of course after updating fpc from cvs, it is right back.

Every month the fpc sources get more exceptions, - sigh -

Show quoted text 5 lines
3. can't find include file "sysutilh.inc" On line 28 of .../fpc/rtl/unix/sysutils.pp sysutilh.inc is included. Lazarus can't find it because it is in a include directory specially for sysutils: .../fpc/rtl/objpas/sysutils. This include path is only used for sysutils.pp.

- sigh -

Mattias

Reply by email

Mattias Gaertner
to Vincent Snijders: I noticed the lazarus codetools have some problems finding declarations when using fpc…
Show quoted text 12 lines
Mattias Gaertner wrote: >>1. oldfpccall is not recognized. >>For example on line 37 of .../fpc/rtl/linux/i386/syscallh.inc: >>function Do_SysCall(sysnr:TSysParam):TSysResult; {$ifndef VER1_0} >>oldfpccall; {$endif} >>oldfpccall is not recognized and parsing stops. > > > ts ts. I thought, introducing new keywords is only a Borland illness. It's not a keyword, it's a modifier ;) Anyways, there is another new one: softfloat; though it applies only to non-i386 architectures :)

ok. What is a softfloat?

Mattias

Reply by email

Vincent Snijders

Hi,

I noticed the lazarus codetools have some problems finding declarations when using fpc 1.9 compiler and sources.

1. oldfpccall is not recognized.
For example on line 37 of .../fpc/rtl/linux/i386/syscallh.inc: function Do_SysCall(sysnr:TSysParam):TSysResult; {$ifndef VER1_0} oldfpccall; {$endif}
oldfpccall is not recognized and parsing stops.

2. wrong signal.inc included
On line 29 of .../fpc/rtl/unix/unix.pp signal.inc is included. This is in the interface section of unix.pp. Lazarus thinks it should include .../fpc/rtl/linux/i386/signal.inc. This is not possible because this file also has some procedure implementation around line 137(which can't be a part of a unit's interface). Apparently the right file to include is .../fpc/rtl/linux/signal.inc. As far as I could see, .../fpc/rtl/linux/i386/signal.inc is not used and might be obsolete. To work around this bug I delete the 'obsolete' file and restart lazarus. Of course after updating fpc from cvs, it is right back.

3. can't find include file "sysutilh.inc"
On line 28 of .../fpc/rtl/unix/sysutils.pp sysutilh.inc is included. Lazarus can't find it because it is in a include directory specially for sysutils: .../fpc/rtl/objpas/sysutils. This include path is only used for sysutils.pp.

Vincent.

Reply by email