Gpc

gpc@gnu.de

5400 discussions

$D directive
by Peter N Lewis 03 Jul '05

03 Jul '05

The warning message for $D is: ignoring BP directive `{$d-}' which is unnecessary in GPC CW Pascal uses $D to turn symbol generation on and off (typically used to disable around sensitive areas of code like password / serial number / authentication / etc). I don't know if there is any equivalent for the Mac directive, but the warning is a bit inaccurate for Mac. Perhaps it should just be the normal "unknown directive", or perhaps there should be a general scheme for setting ignored directives (which could include $D for BP, and could include $unused for Mac). Or perhaps the warning message should just be changed a little? Enjoy, Peter. -- <http://www.stairways.com/> <http://download.stairways.com/>

1 1

Dropping some misfeatures in for-loops and `absolute' variables
by Frank Heckenbach 02 Jul '05

02 Jul '05

GPC accepts the following program, but produces quite silly results: program Foo; var a: array [1 .. 2] of Integer value (0, 0); i: Integer; begin i := 1; for a[i] := 1 to 10 do begin WriteLn (i, ' ', a[i]); if a[i] = 5 then i := 2 end end. The problem is that it evaluates the index i each time, not once before the loop. It would be possible to fix it, but do we really want that? Neither BP nor CP/EP allow it, they allow only identifiers in for-loops. Waldek and I see no need for such a feature. (If it made it possible to nest a compile-time-unknown number of `for' loops, I could see some point, but of course, it doesn't.) So, would anybody mind dropping this misfeature, and requiring an identifier in for-loop counters? The same (and probably a lot of other weird stuff) can be achieved with "extended" `absolute' variables, such as: program Foo; var a: array [1 .. 2] of Integer value (0, 0); i: Integer; {$local W-} c: Integer absolute a[i]; {$endlocal} begin i := 1; for c := 1 to 10 do begin WriteLn (i, ' ', c); if a[i] = 5 then i := 2 end end. We support `absolute' for BP compatibility, but IMHO then we should restrict it to what BP requires, i.e. really absolute addresses, or the address of entire variables or parameters. I suppose (hope) few users actually knew about the extended (mis)features GPC allowed, so I hope we can drop them. (If not, we probably should change semantics to evaluate the address once, and not on each usage, as is done now, so if you rely on this behaviour, you might have to change your code anyway -- if nothing else helps, you can always achieve the same effect with type-casting of pointers.) BP compatible code will not be affected. Any objections? Frank -- Frank Heckenbach, frank(a)g-n-u.de http://fjf.gnu.de/ GnuPG and PGP keys: http://fjf.gnu.de/plan (7977168E)

10 13

$no-methods-always-virtual
by Adriaan van Os 30 Jun '05

30 Jun '05

Peter N. Lewis pointed me to the following: {$methods-always-virtual} {allowed} {$no-methods-always-virtual} {error message} program P; begin end. GPC accepts {$methods-always-virtual} as a directive in source code, but it rejects {$no-methods-always-virtual}. Is there a special reason why ? The value of the flag changes also (I think) when switching from {$mac-pascal} to {$gnu-pascal}. Regards, Adriaan van Os

2 1

Fw: Wikipedia
by Frank Heckenbach 29 Jun '05

29 Jun '05

Scott A. Moore wrote me: > So I've been upgrading the Pascal pages on Wikipedia > recently. I can't help but notice that GPC is almost entirely > unmentioned. Even many DEAD Pascal editions have a page. > > Just a thought. Thanks for the notice, Scott. Anyone here on the list feels like writing a bit (http://en.wikipedia.org/wiki/Pascal_programming_language)? Of course, you can also write on the pages for other languages that you know. Frank -- Frank Heckenbach, frank(a)g-n-u.de http://fjf.gnu.de/ GnuPG and PGP keys: http://fjf.gnu.de/plan (7977168E)

1 0

Question on a warning
by Pascal Viandier 28 Jun '05

28 Jun '05

Hello, When compiling a Pascal source with gpc, I receive the following warning: gpc -g -O0 -D_DEBUG --setlimit=2000 --unit-path=gpi:gpc --gpi-destination-path=gpi --implementation-only -D_DBG -Icommon/include -Imain/include -I/data2/informix-7.31.UD6/include -I/data2/informix-7.31.UD6/incl/esql -I/usr/local/devapps/ISAM/include -c common/src/fdb.pas -o obj/dbg/fdb.o common/src/fdb.pas: In procedure `CreeFDB': common/src/fdb.pas:1041: warning: `for' loop counter is threatened in a subroutine And here is the code that triggers the warning: FOR I := PosARec TO NbChamps DO BEGIN IF ((Champs[I].TipeNb > 1) AND (I <> PosARec)) THEN BEGIN WRITELN('Error: Array in an Array of Records! (line:', Line,')'); RETURN; END; Champs[I].Pos := Champs[I].Pos + AjusARec; Champs[I].TipeNb := TipeNb; Champs[I].DifByte := NbByteARec; END; The code inside the 'for' loop does not call any subroutine, except WriteLn and Return (conditionally) and they don't make any use of the counter. I wonder how the loop counter may be threatened in any way... My question is: did I missed something, or is gpc so delicate that one cannot use a 'for' loop counter outside of the loop for other purpose (that's the case here, the 'for' loop in the middle of a procedure)? How gpc determines that a 'for' loop counter may be altered in the body of the loop? Thanks Pascal Viandier pascal(a)accovia.com

2 1

error: `prefkeys.gpi' must be recompiled?
by Peter N Lewis 28 Jun '05

28 Jun '05

I'm using gp, and it is giving me the following error: /Source/InterarchySupportBundle.p:18: error: `prefkeys.gpi' must be recompiled Clearly this is actually a gpc error. I've attached a -v3 output from gp. Interestingly, it ends with: /Source/PrefKeys.p: recompiling because interface of `GPCMacOSAll.pas' has changed /Source/InterarchySupportBundle.p: recompiling because an interface used indirectly has changed and then proceeds to compile InterarchySupportBundle.p, so GPC may well be quite correct that PrefKeys.p does indeed need recompiling and gp either skipped it for some reason or is doing it in the wrong order. Any ideas as to why this might happen or what I should look in to to try to debug the cause? I'm guessing that the cyclic dependencies (in the implementation section) are causing problems. Peter. gp -v3 -g -gstabs -O0 --uses=GPCMacOSAll --no-check-platform -DINTERARCHY -Wall --unit-path=/Developer/Pascal/GPCPInterfaces:/Source/PNLLibraries:/Source/MacOSXSupport:/Source:/Build --object-path=/IAObjects --unit-destination-path=/IAObjects --Pascal=--include=/Source/PNLLibraries/Prefix.GPC --c=-no-cpp-precomp --c=-I/Developer/Headers/FlatCarbon --c=-I/usr/include/libxml2 --c=-flat_namespace /Source/URLFiles.p gpc -dumpmachine gpc -dumpversion gpc -print-file-name=units gpc --print-needed-options -x Preprocessed-Pascal /var/tmp/GPaaa00594 Needed option for GPC: -D__ppc__ Needed option for GPC: -D__POWERPC__ Needed option for GPC: -D__NATURAL_ALIGNMENT__ Needed option for GPC: -D__MACH__ Needed option for GPC: -D__APPLE__ /Source/URLFiles.p: compiling because target files not found or not up to date /Source/BaseGlobals.p: compiling because target files not found or not up to date /Source/Logs.p: compiling because target files not found or not up to date /Source/PNLLibraries/MyCleverAlerts.p: compiling because target files not found or not up to date /Source/PNLLibraries/MyInternetConfig.p: recompiling interface because source has changed /Source/PNLLibraries/MyInternetConfig.p: compiling because target files not found or not up to date /Source/PNLLibraries/MyKeychain.p: compiling implementation because target files not found or not up to date /Source/PNLLibraries/MyScrap.p: compiling implementation because target files not found or not up to date /Source/PNLLibraries/MyAEUtils.p: compiling implementation because target files not found or not up to date /Source/Utils.p: compiling because target files not found or not up to date /Source/Permissions.p: compiling because target files not found or not up to date /Source/DisplayWindow.p: compiling because target files not found or not up to date /Source/FileMapping.p: compiling implementation because target files not found or not up to date /Source/InterarchyIcons.p: compiling because target files not found or not up to date /Source/PrefKeys.p: compiling implementation because target files not found or not up to date /Source/ReportPrinting.p: compiling implementation because target files not found or not up to date /Source/TransferMode.p: compiling because target files not found or not up to date /Source/Transcript.p: compiling because target files not found or not up to date /Source/PNLLibraries/MyCarbonEvents.p: compiling because target files not found or not up to date /Source/PNLLibraries/MyControls.p: compiling because target files not found or not up to date /Source/PNLLibraries/MyNotifier.p: compiling because target files not found or not up to date /Source/PNLLibraries/MyProcesses.p: recompiling interface because source has changed /Source/PNLLibraries/MyProcesses.p: compiling because target files not found or not up to date /Source/PNLLibraries/MyUnicode.p: compiling because target files not found or not up to date /Source/InterarchyInterface.p: compiling because target files not found or not up to date /Source/PNLLibraries/MyDrag.p: compiling because target files not found or not up to date /Source/PNLLibraries/MyWindow.p: compiling because target files not found or not up to date /Source/ActionToolbarItem.p: compiling because target files not found or not up to date /Source/EditWith.p: compiling because target files not found or not up to date /Source/Resume.p: compiling because target files not found or not up to date /Source/TransferActions.p: compiling because target files not found or not up to date /Source/TransferProgress.p: compiling because target files not found or not up to date /Source/URLMapping.p: compiling because target files not found or not up to date /Source/ViewWith.p: compiling because target files not found or not up to date /Source/GenericBookmarkWindow.p: compiling because target files not found or not up to date /Source/TransferNotificationCenter.p: compiling because target files not found or not up to date /Source/PNLLibraries/MyTextDisplayWindow.p: compiling because target files not found or not up to date /Source/PNLLibraries/MyAppearance.p: compiling because target files not found or not up to date /Source/PNLLibraries/MyHIToolbar.p: compiling because target files not found or not up to date /Source/BookmarkManager.p: compiling because target files not found or not up to date /Source/PNLLibraries/MyApplication.p: compiling because target files not found or not up to date /Source/PNLLibraries/MyEditTextToolbarItem.p: compiling because target files not found or not up to date /Source/PNLLibraries/MyHIView.p: compiling because target files not found or not up to date /Source/PNLLibraries/MyNavigation.p: compiling because target files not found or not up to date /Source/PNLLibraries/MySegmentedView.p: compiling because target files not found or not up to date /Source/SendRecordedCommand.p: compiling because target files not found or not up to date /Source/TemporaryFiles.p: compiling because target files not found or not up to date /Source/CheckWebWindow.p: compiling because target files not found or not up to date /Source/DirectoryList.p: compiling because target files not found or not up to date /Source/DirectoryPathList.p: compiling because target files not found or not up to date /Source/DirectoryRemoveList.p: compiling because target files not found or not up to date /Source/DirectorySpecList.p: compiling because target files not found or not up to date /Source/HTTPPathList.p: compiling because target files not found or not up to date /Source/HTTPPathSuccess.p: compiling because target files not found or not up to date /Source/MirrorCache.p: compiling because target files not found or not up to date /Source/MirrorFileCollection.p: compiling because target files not found or not up to date /Source/MirrorFTPDiskPathList.p: compiling because target files not found or not up to date /Source/MirrorPutMembers.p: compiling because target files not found or not up to date /Source/MirrorPutPathList.p: compiling because target files not found or not up to date /Source/MirrorReportWindow.p: compiling because target files not found or not up to date /Source/PNLLibraries/MySuspendedEvents.p: compiling because target files not found or not up to date /Source/NotifyUser.p: compiling because target files not found or not up to date /Source/ParseFTPList.p: compiling because target files not found or not up to date /Source/ParseHTMLFile.p: compiling because target files not found or not up to date /Source/Transfer.p: compiling because target files not found or not up to date /Source/TransferUtils.p: compiling because target files not found or not up to date /Source/PNLLibraries/MyCustomControl.p: compiling because target files not found or not up to date /Source/PNLLibraries/MyDataBrowser.p: compiling because target files not found or not up to date /Source/PNLLibraries/MyTextDisplay.p: compiling because target files not found or not up to date /Source/AutoUploadsEngine.p: compiling because target files not found or not up to date /Source/BookmarksBar.p: compiling because target files not found or not up to date /Source/ChasingArrows.p: compiling because target files not found or not up to date /Source/FTPDiskScriptingSupport.p: compiling because target files not found or not up to date /Source/FTPDisksEngine.p: compiling because target files not found or not up to date /Source/QueueManager.p: compiling because target files not found or not up to date /Source/ScheduledBookmarksEngine.p: compiling because target files not found or not up to date /Source/SplitViewControl.p: compiling because target files not found or not up to date /Source/StartupItems.p: compiling because target files not found or not up to date /Source/FileActions.p: compiling because target files not found or not up to date /Source/PNLLibraries/MyCharsets.p: compiling because target files not found or not up to date /Source/PNLLibraries/MyTXNControl.p: compiling because target files not found or not up to date /Source/PNLLibraries/MyPlayAsyncSound.p: compiling because target files not found or not up to date /Source/HostInfoMapping.p: compiling implementation because target files not found or not up to date /Source/HostUploadPermissionsMapping.p: compiling implementation because target files not found or not up to date /Source/PNLLibraries/MyDataBrowserColumnView.p: compiling because target files not found or not up to date /Source/PNLLibraries/MyDataBrowserIconView.p: compiling because target files not found or not up to date /Source/PNLLibraries/MyFind.p: compiling because target files not found or not up to date /Source/ScheduleWindow.p: compiling because target files not found or not up to date /Source/PrefKeys.p: recompiling because interface of `GPCMacOSAll.pas' has changed /Source/InterarchySupportBundle.p: recompiling because an interface used indirectly has changed Compiling InterarchySupportBundle.p (603) gpc -D__ppc__ -D__POWERPC__ -D__NATURAL_ALIGNMENT__ -D__MACH__ -D__APPLE__ -g -gstabs -O0 -DINTERARCHY -Wall --unit-path=/Developer/Pascal/GPCPInterfaces:/Source/PNLLibraries:/Source/MacOSXSupport:/Source:/Build --object-path=/IAObjects --include=/Source/PNLLibraries/Prefix.GPC -I /IAObjects -I /IAObjects/ -I /Developer/Pascal/GPCPInterfaces -I /Source/PNLLibraries -I /Source/MacOSXSupport -I /Source -I /Build -I /IAObjects/ -I . -I /Developer/Pascal/gpc-20050331/lib/gcc/powerpc-apple-darwin8.1.0/3.4.3/units -I /Source/ --unit-path=/Source/ --gpi-destination-path=/IAObjects/ --unit-path=/IAObjects/ --no-automake -c -o /IAObjects/InterarchySupportBundle.o /Source/InterarchySupportBundle.p --uses=GPCMacOSAll /Source/InterarchySupportBundle.p:18: error: `prefkeys.gpi' must be recompiled -- <http://www.stairways.com/> <http://download.stairways.com/>

1 0

gpc crash
by Peter N Lewis 28 Jun '05

28 Jun '05

The following program (with an error in it) crashes the compiler. The error (BSET undeclared) is detected, but then the compiler crashes trying to bail out. I'm using gpc-20050331/gcc-3.4.3 with the delphi object patch. Program, execution, and crash report follows. Peter. program peterM; type MyCollection = object function GetDataHandle: Integer; end; function MyCollection.GetDataHandle: Integer; var flags: longint; begin flags := 0; BSET(flags, 16); GetDataHandle := flags; end; begin WriteLn( 'OK' ); end. gpc -o peterM peterM.pas peterM.pas: In method `MyCollection.GetDataHandle': peterM.pas:14: error: undeclared identifier `BSET' (first use in this routine) peterM.pas:14: error: (Each undeclared identifier is reported only once peterM.pas:14: error: for each routine it appears in.) peterM.pas:15: confused by earlier errors, bailing out [crash] Date/Time: 2005-06-27 12:32:35.975 +0800 OS Version: 10.4.1 (Build 8B15) Report Version: 3 Command: gpc1 Path: /Developer/Pascal/gpc-20050331/libexec/gcc/powerpc-apple-darwin8.1.0/3.4.3/gpc1 Parent: gpc [2697] Version: ??? (???) PID: 2699 Thread: 0 Exception: EXC_BAD_ACCESS (0x0001) Codes: KERN_PROTECTION_FAILURE (0x0002) at 0x00000034 Thread 0 Crashed: 0 gpc1 0x0005324c expand_pascal_assignment + 288 (statements.c:1116) 1 gpc1 0x00009048 yyuserAction + 22488 (parse.c:4561) 2 gpc1 0x00010f9c main_yyparse + 544 (parse.c:7900) 3 gpc1 0x000c17c4 toplev_main + 1976 (toplev.c:1826) 4 gpc1 0x00002438 _start + 344 (crt.c:272) 5 gpc1 0x000022dc start + 60 Thread 0 crashed with PPC Thread State: srr0: 0x0005324c srr1: 0x0200f930 vrsave: 0x00000000 cr: 0x44004242 xer: 0x00000000 lr: 0x00053138 ctr: 0x00008ff4 r0: 0x00000028 r1: 0xbfffed00 r2: 0x00000000 r3: 0x40d29078 r4: 0x40d21e00 r5: 0xfefefeff r6: 0x80808080 r7: 0x00000000 r8: 0x00000000 r9: 0x40d26000 r10: 0x40d25b80 r11: 0x40d25b80 r12: 0x00008080 r13: 0x0033ad0c r14: 0x003455d8 r15: 0x00000001 r16: 0x0044bca8 r17: 0x0033a2fc r18: 0x00300d84 r19: 0x00000190 r20: 0x00300d84 r21: 0x00345be4 r22: 0x404cc4bc r23: 0x00000029 r24: 0xa0001bc8 r25: 0x00340d84 r26: 0x00000000 r27: 0x00000000 r28: 0x40d21e00 r29: 0x40d26f80 r30: 0x40d29078 r31: 0x00053138 Binary Images Description: 0x1000 - 0x443fff gpc1 /Developer/Pascal/gpc-20050331/libexec/gcc/powerpc-apple-darwin8.1.0/3.4.3/gpc1 0x40b54000 - 0x40b5bfff libintl.3.dylib /usr/local/lib/libintl.3.dylib 0x8fe00000 - 0x8fe50fff dyld 43 /usr/lib/dyld 0x90000000 - 0x901a6fff libSystem.B.dylib /usr/lib/libSystem.B.dylib 0x901fe000 - 0x90202fff libmathCommon.A.dylib /usr/lib/system/libmathCommon.A.dylib 0x90727000 - 0x90800fff com.apple.CoreFoundation 6.4.1 (368.1) /System/Library/Frameworks/CoreFoundation.framework/Versions/A/CoreFoundation 0x9084b000 - 0x9094dfff libicucore.A.dylib /usr/lib/libicucore.A.dylib 0x909a7000 - 0x90a2bfff libobjc.A.dylib /usr/lib/libobjc.A.dylib 0x90ae3000 - 0x90af5fff libauto.dylib /usr/lib/libauto.dylib 0x91d33000 - 0x91d53fff libmx.A.dylib /usr/lib/libmx.A.dylib 0x92c9b000 - 0x92d89fff libiconv.2.dylib /usr/lib/libiconv.2.dylib 0x93614000 - 0x9361cfff libgcc_s.1.dylib /usr/lib/libgcc_s.1.dylib Model: PowerMac7,3, BootROM 5.1.8f7, 2 processors, PowerPC G5 (3.0), 2 GHz, 1.5 GB Graphics: GeForce FX 5200, GeForce FX 5200, AGP, 64 MB Memory Module: DIMM0/J11, 256 MB, DDR SDRAM, PC3200U-30330 Memory Module: DIMM1/J12, 256 MB, DDR SDRAM, PC3200U-30330 Memory Module: DIMM2/J13, 512 MB, DDR SDRAM, PC3200U-30330 Memory Module: DIMM3/J14, 512 MB, DDR SDRAM, PC3200U-30330 Modem: Jump, , V.92, Version 1.0, Network Service: Built-in Ethernet, Ethernet, en0 Serial ATA Device: ST3160023AS, 149.05 GB Parallel ATA Device: HL-DT-ST DVD-RW GWA-4082B, USB Device: CanoScan, Canon, Up to 12 Mb/sec, 500 mA USB Device: Hub, , Up to 12 Mb/sec, 500 mA USB Device: CF076, CF076, Up to 12 Mb/sec, 500 mA USB Device: Hub in Apple Pro Keyboard, Chicony, Up to 12 Mb/sec, 500 mA USB Device: Apple Optical USB Mouse, Logitech, Up to 1.5 Mb/sec, 100 mA USB Device: Apple Pro Keyboard, Chicony, Up to 12 Mb/sec, 250 mA USB Device: Studio Display, , Up to 1.5 Mb/sec, 500 mA -- <http://www.stairways.com/> <http://download.stairways.com/>

2 2

"reference expected, value given" weird error
by Peter N Lewis 27 Jun '05

27 Jun '05

The following gives the error "reference expected, value given", which is very confusing (it took me ages to spot the problem as being a mismatched procedure type in one of the parameters. I realize error messages are often very difficult, and it looks like in this case, the error was actually changed from "type mismatch in argument 1 of" (see Subject: Protected Var parameter bug in the list archives). You can mark this as a low priority, but it took me quite a while to figure out what was wrong. Peter. gpc -c peterS.pas peterS.pas: In main program: peterS.pas:25: error: reference expected, value given // This program is meant to fail to compile, but would hopefully display a better error message. program PeterS; type SInt16 = Integer attribute( size = 16 ); function InitIcons( var msg: SInt16 ): Integer; begin return 0; end; type StartupInitProc = function( var msg: Integer ): Integer; procedure SetStartup( init: StartupInitProc ); begin end; begin SetStartup( InitIcons ); end. -- <http://www.stairways.com/> <http://download.stairways.com/>

1 0

Which gpc version is recommended for windows (C and pascal code parts)?
by Peter Radloff 26 Jun '05

26 Jun '05

Hi everybody, I want to start porting a old DOS application written with Metaware Pascal and some C to Windows. I have found gcc 3.2.3 and gpc for the same gcc version (last year). Is this the recommend stable version? Is gpc support complete dead now? No compiled version available for download anymore. No WEB site update,... no hints, archive of mailing list broken long time. Please can somebody give a statement what happend with gpc. I am not sure is gpc the right compiler for this port, if nobody support it. On the other site i like to use of gcc compiler. Only if there is no other way i will switch to Free Pascal or Delphi. Thanks Peter

4 5

Unix compatibility
by Rick Engebretson 26 Jun '05

26 Jun '05

While trying to learn and exploit the unix (linux) platform, my google searches have turned up ms.net references (for example named pipes or fifos). MS is re-learning unix. In unix, software is built as small programs (tools) and assembled via scripting languages into executables. Tool instances are managed as "processes" by the OS itself. This script level approach is similar to compiled level classes, polymorphism, encapsulation, etc, of other languages. But of course, scripts are far simpler and more flexible. Many of these unix tools are quite old, but still useful. For example the cron program is a background job scheduler. Where modern pascal works so well is in building new compiled unix tools. C is just not an option for most applications programmers. So I am less concerned with "new" features than I am with stability and clarity. Both GPC and FPC are fantastic contributions to the world's technical community (on the linux platform). The learning process is very long, so stability and clarity are essential.

6 6

Jump to page:

2025

2024

2023

2022

2021

2020

2019

2018

2017

2016

2015

2014

2013

2012

2011

2010

2009

2008

2007

2006

2005

2004

2003

2002

2001

2000

1999

1998

1997

1996

1995

Gpc