Send fpc-pascal mailing list submissions to To subscribe or unsubscribe via the World Wide Web, visit http://lists.freepascal.org/mailman/listinfo/fpc-pascal or, via email, send a message with subject or body 'help' to You can reach the person managing the list at When replying, please edit your Subject line so it is more specific than "Re: Contents of fpc-pascal digest..." Today's Topics: 1. advanced macros? (Roland Schaefer) 2. Re: advanced macros? (Jonas Maebe) 3. Re: advanced macros? (Marco van de Voort) 4. Re: Linking issue in Ubuntu 9.04 (32 bit) (Alan Krause) 5. Error attempting to build FPC from svn (Alan Krause) 6. ifdef'ing FreeBSD by os version number (Marc Santhoff) 7. Re: Error attempting to build FPC from svn (Jonas Maebe) 8. Re: fpc-pascal Digest, Vol 60, Issue 47 (Richard Jasmin) ---------------------------------------------------------------------- Message: 1 Date: Tue, 07 Jul 2009 13:57:16 +0200 From: Roland Schaefer Subject: [fpc-pascal] advanced macros? To: fpc-pascal Message-ID: Content-Type: text/plain; charset=ISO-8859-1 Hi, reading the Programmer's Manual, I get the impression that C-style macros with {$MACRO ON} cannot do things like C #define MY_MACRO(param1,param2...) code_with ( param1 && param 2 ); i.e., passing strings macros for in-macro insertion. Is this true? If yes, are there any plans to include such capabilities in the preprocessor? It would be very useful in places. On the other hand, the mighty preprocessor is one of the primary obfuscation "tools" in C. One related question: In current FPC macros, can I include {$IFDEF}s? I did it, and without using the macro, the unit compiles ok, but I get various errors whenever I use the macro. Cheers, thanks a lot Roland ------------------------------ Message: 2 Date: Tue, 7 Jul 2009 14:13:59 +0200 From: Jonas Maebe Subject: Re: [fpc-pascal] advanced macros? To: , FPC-Pascal users discussions Message-ID: Content-Type: text/plain; charset=US-ASCII; format=flowed On 07 Jul 2009, at 13:57, Roland Schaefer wrote: > reading the Programmer's Manual, I get the impression that C-style > macros with {$MACRO ON} cannot do things like C > > #define MY_MACRO(param1,param2...) > code_with ( param1 && param 2 ); > > i.e., passing strings macros for in-macro insertion. Is this true? > Yes. > If > yes, are there any plans to include such capabilities in the > preprocessor? > No. > One related question: In current FPC macros, can I include {$IFDEF}s? > I doubt it, as I don't think that the preprocessing happens recursively. Jonas ------------------------------ Message: 3 Date: Tue, 7 Jul 2009 14:42:02 +0200 (CEST) From: (Marco van de Voort) Subject: Re: [fpc-pascal] advanced macros? To: , FPC-Pascal users discussions Message-ID: Content-Type: text/plain; charset="US-ASCII" In our previous episode, Roland Schaefer said: > i.e., passing strings macros for in-macro insertion. Is this true? If > yes, are there any plans to include such capabilities in the > preprocessor? It would be very useful in places. On the other hand, the > mighty preprocessor is one of the primary obfuscation "tools" in C. > It is not that much needed anyway. Generics and inline functions do most of the stuff that the preprocessor is used for in C. Also the fact that visibility of identifiers (importing of other compilation units) is not include based makes it somewhat less useful as many people think. The only place where I miss it somewhat is in laying out complex structured constants, preferably in some friendly way. > One related question: In current FPC macros, can I include {$IFDEF}s? I > did it, and without using the macro, the unit compiles ok, but I get > various errors whenever I use the macro. > Not that I know, but you of course can define it under such: {$ifdef mydef} {$define macro:=something} {$else} {$define macro:=something2} {$endif} But that is on the place of macro definition, not "local". ------------------------------ Message: 4 Date: Tue, 7 Jul 2009 09:21:46 -0700 From: Alan Krause Subject: [fpc-pascal] Re: Linking issue in Ubuntu 9.04 (32 bit) To: FPC-Pascal users discussions Message-ID: Content-Type: text/plain; charset="iso-8859-1" Just a quick update on this issue. I finally decided to submit a bug report via Ubuntu's Launchpad, as I didn't see any other similar bugs in their database. ( Bug report is here: https://bugs.launchpad.net/bugs/392197 ) It looks as if the issue has now been resolved and the fix is available for the next release (9.10 - Karmic Koala). However, I was able to download the appropriate .DEB file for my architecture and install it on a 9.04 box, and it does appear to work as advertised. Alan On Fri, Apr 24, 2009 at 1:39 PM, Alan Krause wrote: > I've installed ubuntu 9.04 in a VM to test it out, and have installed fpc > 2.2.4. It is always good to look before you leap, right? > > Anyhow, I am trying to compile an existing project that works fine under > Ubuntu 8.04. I can get all of the unit to compile, but when it comes time= > to > link them together into a shared library, I get the following: > > Linking libproj.so > Error: Can't call the linker, switching to external linking > Fatal: There were 1 errors compiling module, stopping > Fatal: Compilation aborted > Error: /usr/local/bin/ppc386 returned an error exitcode (normal if you did > not specify a source file to be compiled) > > Here is the source code for the sample project: > > library project1; > > uses > Classes; > > function dRound(iDec: integer; dRate: double): double; > const > TenToPower: Array[0..9] of integer =3D (1, 10, 100, 1000, 10000, 100000, > 1000000, 10000000, 100000000, > 1000000000); > var > dInc : double; > begin > if iDec > 0 then begin > dInc :=3D 0.5000001; > result :=3D trunc (dRate * (TenToPower [iDec]) + dInc) / > TenToPower [iDec]; > end else begin > result :=3D dRate; > end ; > end; > > function one : double; cdecl; > begin > Result :=3D dRound( 2, 0.529 ) ; > end; > > begin > end. > > And the command I use to compile it is: > fpc -Sd -Cg -O3 proj.pas > > Anyone else having similar issues? > > Alan > > -------------- next part -------------- An HTML attachment was scrubbed... URL: http://lists.freepascal.org/lists/fpc-pascal/attachments/20090707/72c3= bbb6/attachment.html ------------------------------ Message: 5 Date: Tue, 7 Jul 2009 09:25:41 -0700 From: Alan Krause Subject: [fpc-pascal] Error attempting to build FPC from svn To: FPC-Pascal users discussions Message-ID: Content-Type: text/plain; charset="iso-8859-1" I am attempting to build FPC from svn (trunk) and receive the following error message while attempting to build the gtk2 package: pangoincludes.inc(14,2) Fatal: Can't open include file "pango-glyph-item.inc" It appears as if perhaps a file is missing from the repository? Alan -------------- next part -------------- An HTML attachment was scrubbed... URL: http://lists.freepascal.org/lists/fpc-pascal/attachments/20090707/6630= 619c/attachment-0001.htm ------------------------------ Message: 6 Date: Tue, 07 Jul 2009 22:45:03 +0200 From: Marc Santhoff Subject: [fpc-pascal] ifdef'ing FreeBSD by os version number To: FPC-Pascal users discussions Message-ID: Content-Type: text/plain; charset=UTF-8 Hi, are there flags defined in the fpc sources for discriminating different os versions? While translating some structures from the systems USB headers I found changes, some fields added and the like. This needs to be reflected in the translation. Version in question are FreeBSD4, 6 and 7 currently. TIA,