Re: [fpc-pascal] Mozilla XPCOM
Marcos Douglas escreveu: On Tue, Jun 8, 2010 at 12:55 PM, Luiz Americo Pereira Camara wrote: Marcos Douglas escreveu: Hi Luiz, On Mon, Jun 7, 2010 at 10:35 PM, Luiz Americo Pereira Camara wrote: Take a look at http://lazarusroad.blogspot.com/2008/11/effect-of-using-constant-parameter-for.html Then, this continue true how I said in other mail: On Mon, Jun 7, 2010 at 11:59 AM, Marcos Douglas wrote: Always use 'const' for 'strings' because this is faster. Strings will be passed by reference. And about not string types, is more faster too? eg: foo (const i: Integer) No. I did this test too. Double should also benefit but the generated assembler is equal with or without const. Exactly. Therefore I always used 'const' only at 'strings' params. I thought it had changed, but not. ;-) It can be useful for record parameters also Luiz ___ fpc-pascal maillist - fpc-pascal@lists.freepascal.org http://lists.freepascal.org/mailman/listinfo/fpc-pascal
Re: [fpc-pascal] Mozilla XPCOM
On Tue, Jun 8, 2010 at 12:55 PM, Luiz Americo Pereira Camara wrote: > Marcos Douglas escreveu: >> >> Hi Luiz, >> >> On Mon, Jun 7, 2010 at 10:35 PM, Luiz Americo Pereira Camara >> wrote: >> >>> >>> Take a look at >>> >>> http://lazarusroad.blogspot.com/2008/11/effect-of-using-constant-parameter-for.html >>> >>> >> >> Then, this continue true how I said in other mail: >> >> On Mon, Jun 7, 2010 at 11:59 AM, Marcos Douglas wrote: >> >>> >>> Always use 'const' for 'strings' because this is faster. Strings will >>> be passed by reference. >>> >> >> And about not string types, is more faster too? eg: foo (const i: Integer) >> > > No. I did this test too. Double should also benefit but the generated > assembler is equal with or without const. Exactly. Therefore I always used 'const' only at 'strings' params. I thought it had changed, but not. ;-) Marcos Dougla ___ fpc-pascal maillist - fpc-pascal@lists.freepascal.org http://lists.freepascal.org/mailman/listinfo/fpc-pascal
[fpc-pascal] Lazarus and Freepascal meeting, june 26, The Netherlands
Hi all, On the 26th of june there is a meeting for the Lazarus and Freepascal developers in the Netherlands. The developers who have time and the possibility to come to the Netherlands will be there, to see each other in the 'real world'. And to discuss ideas and new developments around Freepascal and Lazarus. Discussion by email are not always ideal, this is the moment to alk face-to-face. ;) The meeting is a result of an invitation by the 'HCC Pascal gebruikers groep'. This is a group of Delphi/pascal users who organise regular meetings and also publish the Blaise magazine about Pascal-related languages. They have also joined forces to translate the German Lazarus book to English. All Pascal-loving individuals (in or around The Netherlands) are invited to join us. There are several sessions (in Dutch) for Lazarus/fpc users. But at the same time there is the possibility to discuss and talk about Pascal and all related stuff. There is also the possibility to ask questions to the core-developers. There is an entrance-fee of 50 euros, to cover for the expenses. For this you'll also receive a Lazarus-USB stick to run Lazarus on Windows without any installation and a one-year download subscription of the Blaise magazine (Dutch or English version). More information can be found on the link below. You can also subscribe yourself on that page. http://www.hcc-pgg.nl/index.php?actie=bijeenkomsten/volgende_bijeenkomst I hope to see a lot of (prospective) Lazarus/Freepascal developers on june 26th in the Netherlands. I sincerely think that events like this can help the popularity and development of Pascal. Regards, Joost ___ fpc-pascal maillist - fpc-pascal@lists.freepascal.org http://lists.freepascal.org/mailman/listinfo/fpc-pascal
Re[2]: [fpc-pascal] fpdoc and multiple Include paths issue
Hello FPC-Pascal, Tuesday, June 8, 2010, 2:23:52 PM, you wrote: >> I know, and tried both just too see. But as Jonas has said, FPC >> itself uses >> semi-colon on all platforms, hence the reason I tried semi-colon >> first. JM> The compiler should actually be changed to use the platform-specific JM> separator, because a directory on a unix platform can perfectly JM> contain a semi-colon. A Windows folder can have a ';' also. -- F:\>md "Dot;comma" F:\>dir dot* Volume in drive F is unlabeled Serial number is 40AC:DFAA Directory of F:\dot* 8/06/2010 18:29 Dot;comma 0 bytes in 0 files and 1 dir 15.094.943.744 bytes free - -- Best regards, José ___ fpc-pascal maillist - fpc-pascal@lists.freepascal.org http://lists.freepascal.org/mailman/listinfo/fpc-pascal
Re: [fpc-pascal] fpdoc and multiple Include paths issue
Jonas Maebe schrieb: because a directory on a unix platform can perfectly contain a semi-colon. That applies to Windows too. ___ fpc-pascal maillist - fpc-pascal@lists.freepascal.org http://lists.freepascal.org/mailman/listinfo/fpc-pascal
Re: [fpc-pascal] Mozilla XPCOM
Marcos Douglas escreveu: Hi Luiz, On Mon, Jun 7, 2010 at 10:35 PM, Luiz Americo Pereira Camara wrote: Take a look at http://lazarusroad.blogspot.com/2008/11/effect-of-using-constant-parameter-for.html Then, this continue true how I said in other mail: On Mon, Jun 7, 2010 at 11:59 AM, Marcos Douglas wrote: Always use 'const' for 'strings' because this is faster. Strings will be passed by reference. And about not string types, is more faster too? eg: foo (const i: Integer) No. I did this test too. Double should also benefit but the generated assembler is equal with or without const. Luiz ___ fpc-pascal maillist - fpc-pascal@lists.freepascal.org http://lists.freepascal.org/mailman/listinfo/fpc-pascal
Re: [fpc-pascal] Mozilla XPCOM
Hi Luiz, On Mon, Jun 7, 2010 at 10:35 PM, Luiz Americo Pereira Camara wrote: > > Take a look at > http://lazarusroad.blogspot.com/2008/11/effect-of-using-constant-parameter-for.html > Then, this continue true how I said in other mail: On Mon, Jun 7, 2010 at 11:59 AM, Marcos Douglas wrote: > Always use 'const' for 'strings' because this is faster. Strings will > be passed by reference. And about not string types, is more faster too? eg: foo (const i: Integer) Marcos Douglas PS: Do you write in the list lazarus-br? ___ fpc-pascal maillist - fpc-pascal@lists.freepascal.org http://lists.freepascal.org/mailman/listinfo/fpc-pascal
Re: [fpc-pascal] fpdoc and multiple Include paths issue
Op 2010-06-08 14:23, Jonas Maebe het geskryf: > > The compiler should actually be changed to use the platform-specific > separator, because a directory on a unix platform can perfectly > contain a semi-colon. I guess, but do you really want to go down that route? :-) Linux (and probably other *nix's too) support just about any character in a path or filename - even non-visible escaped characters. In fact, if I am not mistaken Linux supports any character (even escaped or non-visual) except for / and NULL. :-) Regards, - Graeme - -- fpGUI Toolkit - a cross-platform GUI toolkit using Free Pascal http://opensoft.homeip.net/fpgui/ ___ fpc-pascal maillist - fpc-pascal@lists.freepascal.org http://lists.freepascal.org/mailman/listinfo/fpc-pascal
Re: [fpc-pascal] fpdoc and multiple Include paths issue
On 08 Jun 2010, at 14:16, Graeme Geldenhuys wrote: I know, and tried both just too see. But as Jonas has said, FPC itself uses semi-colon on all platforms, hence the reason I tried semi-colon first. The compiler should actually be changed to use the platform-specific separator, because a directory on a unix platform can perfectly contain a semi-colon. Jonas ___ fpc-pascal maillist - fpc-pascal@lists.freepascal.org http://lists.freepascal.org/mailman/listinfo/fpc-pascal
Re: [fpc-pascal] fpdoc and multiple Include paths issue
Op 2010-06-08 13:26, Michael Van Canneyt het geskryf: > > No. You must specify a -Fi per path. It doesn't split the path. Umm, but FPC allows it in fpc.cfg file, so maybe allowing it in fpdoc will be more consistent don't you think. It should be rather easy to add. eg: A sample from FPC generated ~/.fpc.cfg file shows two examples where multiple paths are allowed: - ## searchpath for includefiles #-Fi/pp/inc;/pp/rtl/inc ... # searchpath for libraries -Fl/usr/lib/gcc/i486-linux-gnu/4.0.2 #-Fl/pp/lib #-Fl/lib;/usr/lib - > (coincidentally, the path separator is : on linux, not ; :)) I know, and tried both just too see. But as Jonas has said, FPC itself uses semi-colon on all platforms, hence the reason I tried semi-colon first. Regards, - Graeme - -- fpGUI Toolkit - a cross-platform GUI toolkit using Free Pascal http://opensoft.homeip.net/fpgui/ ___ fpc-pascal maillist - fpc-pascal@lists.freepascal.org http://lists.freepascal.org/mailman/listinfo/fpc-pascal
Re: [fpc-pascal] fpdoc and multiple Include paths issue
On 08 Jun 2010, at 13:26, Michael Van Canneyt wrote: No. You must specify a -Fi per path. It doesn't split the path. (coincidentally, the path separator is : on linux, not ; :)) At least for the fpc/ppcXXX binaries, the path separator is ";" on all platforms. Jonas ___ fpc-pascal maillist - fpc-pascal@lists.freepascal.org http://lists.freepascal.org/mailman/listinfo/fpc-pascal
Re: [fpc-pascal] fpdoc and multiple Include paths issue
On Tue, 8 Jun 2010, Graeme Geldenhuys wrote: Hi Is fpdoc supposed to handle multiple include paths with one -Fi parameter? eg: --input='-Fi../src/corelib;../src/corelib/x11 ../src/corelib/fpg_utils.pas' --descr=xml/corelib/fpg_utils.xml \ The above line fails. fpdoc cannot find the include file used my fpg_utils.pas unit. Changing that line to rather use two -Fi parameters seems to fix it. But isn't fpdoc supposed to can handle multiple paths in one -Fi param? No. You must specify a -Fi per path. It doesn't split the path. (coincidentally, the path separator is : on linux, not ; :)) Michael. ___ fpc-pascal maillist - fpc-pascal@lists.freepascal.org http://lists.freepascal.org/mailman/listinfo/fpc-pascal
[fpc-pascal] fpdoc and multiple Include paths issue
Hi Is fpdoc supposed to handle multiple include paths with one -Fi parameter? eg: --input='-Fi../src/corelib;../src/corelib/x11 ../src/corelib/fpg_utils.pas' --descr=xml/corelib/fpg_utils.xml \ The above line fails. fpdoc cannot find the include file used my fpg_utils.pas unit. Changing that line to rather use two -Fi parameters seems to fix it. But isn't fpdoc supposed to can handle multiple paths in one -Fi param? The modified (and fixed) version of the above line: --input='-Fi../src/corelib -Fi../src/corelib/x11 ../src/corelib/fpg_utils.pas' --descr=xml/corelib/fpg_utils.xml \ I'm using fpdoc from FPC 2.4.1 and FPC 2.5.1 under Linux. -- Regards, - Graeme - ___ fpGUI - a cross-platform Free Pascal GUI toolkit http://opensoft.homeip.net/fpgui/ ___ fpc-pascal maillist - fpc-pascal@lists.freepascal.org http://lists.freepascal.org/mailman/listinfo/fpc-pascal
[fpc-pascal] Re: FPC 2.4.1 & fpdoc fails to parse code in interface section
Here is another parser error causing fpdoc to fail generating documentation. http://bugs.freepascal.org/view.php?id=16673 -- Regards, - Graeme - ___ fpGUI - a cross-platform Free Pascal GUI toolkit http://opensoft.homeip.net/fpgui/ ___ fpc-pascal maillist - fpc-pascal@lists.freepascal.org http://lists.freepascal.org/mailman/listinfo/fpc-pascal
[fpc-pascal] FPC 2.4.1 & fpdoc fails to parse code in interface section
fpdoc or fcl-passrc seems to be worse of than it was before. I know fcl-passrc was going to be modified for fpdoc, so it only parses the interface section. But the code listed in the bug report IS in the interface section. It can't seem to parse a class definition that contains the 'platform' hint directive in one of its properties. I never had this issue before with older FPC versions, but then I can't remember when I added the platform hint directives to the code. http://bugs.freepascal.org/view.php?id=16672 Any chance of a bug fix before the final 2.4.2 release? -- Regards, - Graeme - ___ fpGUI - a cross-platform Free Pascal GUI toolkit http://opensoft.homeip.net/fpgui/ ___ fpc-pascal maillist - fpc-pascal@lists.freepascal.org http://lists.freepascal.org/mailman/listinfo/fpc-pascal
