Sign in Join

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

Mailing lists / lazarus / 2008-02

Code Explorer problem with libc unit.

7 messages · 3 people · –

Reply by email Subscribe to this list Your subscription

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

Giuliano Colla

When the libc unit ($FPCSOURCE/rtl/netwlibc/libc.pp) is in the uses clause of a unit, it happens that code explorer gets confused, and whenever you click on "Find Declaration", if the target isn't in the current unit, it opens the libc unit, around a macNS finderInfo record, on the line:

                     0 : ( generic : array[0..31] of byte );

and reports an error:
"An identifier was expected but generic has been found." Commenting out the libc brings back everything to normal.

FPC 2.2.0, platform linux, widgetset irrelevant.

Giuliano

Giuliano Colla Whenever people agree with me, I always feel I must be wrong (O. Wilde)

Reply by email

Mattias Gaertner
to Giuliano Colla
Show quoted text 13 lines
When the libc unit ($FPCSOURCE/rtl/netwlibc/libc.pp) is in the uses clause of a unit, it happens that code explorer gets confused, and whenever you click on "Find Declaration", if the target isn't in the current unit, it opens the libc unit, around a macNS finderInfo record, on the line: 0 : ( generic : array[0..31] of byte ); and reports an error: "An identifier was expected but generic has been found." Commenting out the libc brings back everything to normal. FPC 2.2.0, platform linux, widgetset irrelevant.

Fixed in 14151. Please test.

Mattias

Reply by email

Giuliano Colla
to Mattias Gaertner

Mattias Gaertner ha scritto:

Show quoted text 19 lines
On Thu, 14 Feb 2008 21:17:12 +0100 Giuliano Colla wrote: > When the libc unit ($FPCSOURCE/rtl/netwlibc/libc.pp) is in the uses > clause of a unit, it happens that code explorer gets confused, and > whenever you click on "Find Declaration", if the target isn't in the > current unit, it opens the libc unit, around a macNS finderInfo > record, on the line: > > 0 : ( generic : array[0..31] of byte ); > > and reports an error: > "An identifier was expected but generic has been found." > Commenting out the libc brings back everything to normal. > > FPC 2.2.0, platform linux, widgetset irrelevant. Fixed in 14151. Please test.

I had no doubts :-) , but I tested, and now it works as expected!

Thanks a lot, it was a nuisance to comment/uncomment libc!

Giuliano

Giuliano Colla Whenever people agree with me, I always feel I must be wrong (O. Wilde)

Reply by email

Giuliano Colla
to Mattias Gaertner: On Thu, 14 Feb 2008 21:17:12 +0100 Fixed in 14151. Please test. Mattias

Mattias Gaertner ha scritto:

Show quoted text 19 lines
On Thu, 14 Feb 2008 21:17:12 +0100 Giuliano Colla wrote: > When the libc unit ($FPCSOURCE/rtl/netwlibc/libc.pp) is in the uses > clause of a unit, it happens that code explorer gets confused, and > whenever you click on "Find Declaration", if the target isn't in the > current unit, it opens the libc unit, around a macNS finderInfo > record, on the line: > > 0 : ( generic : array[0..31] of byte ); > > and reports an error: > "An identifier was expected but generic has been found." > Commenting out the libc brings back everything to normal. > > FPC 2.2.0, platform linux, widgetset irrelevant. Fixed in 14151. Please test.

I had made an entry in the bug tracker. Now I've added a note that the issue has been fixed. Maybe someone wants to set it to Resolved.

Giuliano

Giuliano Colla Whenever people agree with me, I always feel I must be wrong (O. Wilde)

Reply by email

Mattias Gaertner
to Giuliano Colla
Show quoted text 23 lines
Mattias Gaertner ha scritto: > On Thu, 14 Feb 2008 21:17:12 +0100 > Giuliano Colla wrote: > >> When the libc unit ($FPCSOURCE/rtl/netwlibc/libc.pp) is in the >> uses clause of a unit, it happens that code explorer gets >> confused, and whenever you click on "Find Declaration", if the >> target isn't in the current unit, it opens the libc unit, around a >> macNS finderInfo record, on the line: >> >> 0 : ( generic : array[0..31] of byte ); >> >> and reports an error: >> "An identifier was expected but generic has been found." >> Commenting out the libc brings back everything to normal. >> >> FPC 2.2.0, platform linux, widgetset irrelevant. > > Fixed in 14151. Please test. > I had made an entry in the bug tracker. Now I've added a note that the issue has been fixed. Maybe someone wants to set it to Resolved.

Thanks for the hint.

Done.

Mattias

Reply by email

Marco van de Voort
to Giuliano Colla: Mattias Gaertner ha scritto: I had no doubts :-) , but I tested, and now it works as…
Giuliano Colla wrote 5 lines
Mattias Gaertner ha scritto: > On Thu, 14 Feb 2008 21:17:12 +0100 > Giuliano Colla wrote: > >> When the libc unit ($FPCSOURCE/rtl/netwlibc/libc.pp)

You are using Novell Netware/libc ? I think you mean packages/libc (formerly packages/extra/libc

Show quoted text 8 lines
>> FPC 2.2.0, platform linux, widgetset irrelevant. > > Fixed in 14151. Please test. > I had no doubts :-) , but I tested, and now it works as expected! Thanks a lot, it was a nuisance to comment/uncomment libc!

Note that leaving that unit uncommented is the best anyway. It is deprecated (former Kylix compability) and linux/x86 specific. IOW it will bring you into problems when going to OS X/Solaris/x86_64-Linux/FreeBSD etc.

Reply by email

Giuliano Colla
to Marco van de Voort

Marco van de Voort ha scritto:

Show quoted text 20 lines
On Sat, Feb 16, 2008 at 01:06:46PM +0100, Giuliano Colla wrote: > Mattias Gaertner ha scritto: >> On Thu, 14 Feb 2008 21:17:12 +0100 >> Giuliano Colla wrote: >> >>> When the libc unit ($FPCSOURCE/rtl/netwlibc/libc.pp) You are using Novell Netware/libc ? I think you mean packages/libc (formerly packages/extra/libc >>> FPC 2.2.0, platform linux, widgetset irrelevant. >> Fixed in 14151. Please test. >> > I had no doubts :-) , but I tested, and now it works as expected! > > Thanks a lot, it was a nuisance to comment/uncomment libc! Note that leaving that unit uncommented is the best anyway. It is deprecated (former Kylix compability) and linux/x86 specific. IOW it will bring you into problems when going to OS X/Solaris/x86_64-Linux/FreeBSD etc.

Thanks, I'm aware of that, but we have a range of Linux specific applications, where cross-platform considerations do not apply, and libc services are handy.

Giuliano

Giuliano Colla Whenever people agree with me, I always feel I must be wrong (O. Wilde)

Reply by email