RE : [fpc-pascal] Re: RE : Re: RE : FPCUp FPC/Lazarus installer/updater: first Linux/Windows version released
> #!/bin/sh > ~/wherever/we/installed/fpc -n > @~/wherever/we/installed/fpc.cfg $* which should instruct our > fpc to ignore any other fpc.cfg, use our own, and get any > other arguments passed to the script. > > Then assign this script as the compiler in Lazarus?!?! > > (I suppose this might not work as Lazarus might be looking > for other files in the compiler path!??!) > The script still picks up 2.4.4 but the idea is good. This works: #!/bin/sh ~/wherever/we/installed/compiler/ppc386 -n @~/wherever/we/installed/fpc.cfg $* It picks up the right compiler but there is still a problem though: fpc.cfg includes the units searchpath ~/wherever/we/installed/units/$fpctarget but make install INSTALL_PREFIX=blah installs in blah/lib/fpc/$fpcversion/units/$fpctarget. Running 'fpcmkcfg -d basepath=~/wherever/we/installed/lib/fpc/2.6.1 ...' solves this. Unfortunately 'basepath=~/wherever/we/installed/lib/fpc/$fpcversion' doesn't work. Lazarus seems to be perfectly happy with the script (I installed it in the fpc/bin directory) > Alternatively, your other suggestion would be doable but > sounds like a lot of work as well ;) > Your solution is much better once the paths are sorted out. One other problem: the debugger is configured as gdb which is not working. Lazarus looks for a gdb in the current directory (whatever that is), not in the path. Using the output of 'which gdb' would be the easiest solution on linux to set up the default gdb. Regarding side by side installations, wouldn't it be better to store the lazarus config in a subdir of the lazarus install? A fixed directory makes side by side installation of lazarus very difficult. Ludo ___ fpc-pascal maillist - fpc-pascal@lists.freepascal.org http://lists.freepascal.org/mailman/listinfo/fpc-pascal
[fpc-pascal] Re: RE : Re: RE : Re: RE : FPCUp FPC/Lazarus installer/updater: first Linux/Windows version released
On 11-2-2012 10:30, Ludo Brands wrote: >> #!/bin/sh >> ~/wherever/we/installed/fpc -n >> @~/wherever/we/installed/fpc.cfg $* which should instruct our >> fpc to ignore any other fpc.cfg, use our own, and get any >> other arguments passed to the script. >> >> Then assign this script as the compiler in Lazarus?!?! > The script still picks up 2.4.4 but the idea is good. This works: > > #!/bin/sh > ~/wherever/we/installed/compiler/ppc386 -n @~/wherever/we/installed/fpc.cfg > $* > > It picks up the right compiler but there is still a problem though: fpc.cfg > includes the units searchpath ~/wherever/we/installed/units/$fpctarget but > make install INSTALL_PREFIX=blah installs in > blah/lib/fpc/$fpcversion/units/$fpctarget. Running 'fpcmkcfg -d > basepath=~/wherever/we/installed/lib/fpc/2.6.1 ...' solves this. > Unfortunately 'basepath=~/wherever/we/installed/lib/fpc/$fpcversion' doesn't > work. Lazarus seems to be perfectly happy with the script (I installed it in > the fpc/bin directory) Ok, I've added this to my todo list http://lazarus.freepascal.org/index.php/topic,15919.0.html In the meantime, patches welcome :) > One other problem: the debugger is configured as gdb which is not working. > Lazarus looks for a gdb in the current directory (whatever that is), not in > the path. Using the output of 'which gdb' would be the easiest solution on > linux to set up the default gdb. Agreed, added to todo list. On Windows, I think the path where make.exe is installed should also give an installed gdb. > Regarding side by side installations, wouldn't it be better to store the > lazarus config in a subdir of the lazarus install? A fixed directory makes > side by side installation of lazarus very difficult. You mean a --primary-config path underneath the lazarus application directory? Could be done in principle. Then again, current fpcup does not have a fixed primary-config-path, merely a default one. I intended to leave the fpc and lazarus svn directories alone as much as possible so a user could delete everything and do a new checkout whenever he wants without touching config files. I realize storing fpcup config files (e.g. SVN urls, etc) in the lazarus and/or fpc svn dirs may not be desirable - if we follow that strategy. An alternative could be to use an fpcup config file stored wherever config files are stored on the os (forgot the function in FPC). Then use a default profile and allow the user to add profiles (e.g. using --saveasprofile=bla). User can invoke with --profile=bla. This will allow the GUI to also easily retrieve a list of side-by-side installs... Regards, Reinier ___ fpc-pascal maillist - fpc-pascal@lists.freepascal.org http://lists.freepascal.org/mailman/listinfo/fpc-pascal
[fpc-pascal] Adding Notes in FPDoc
Hi, Seeing the discussions about annotating the documentation created by FPDoc, I added support for notes. (revision 20304) In short: At the level of the , and tags, you can now include a tag. Within the tag, you can include one or more tags. They are typeset as an unordered list, which means that it can basically contain the same things as a element. (so no tables, code blocks and what not). By default, the tag is ignored. Only if you give fpdoc the --emit-notes option, then the notes will be included in the output. (at least in HTML and all linear output). The fpdoc XML project file also supports the emit-notes option. I have documented all this it in the official fpdoc reference guide. (rev. 890) As a side note: The official FPC documentation will not contain notes in the output. I consider them for private use only, so it is useless to submit notes. But I can understand other people want such a feature, therefor I added it to fpdoc. Michael. ___ fpc-pascal maillist - fpc-pascal@lists.freepascal.org http://lists.freepascal.org/mailman/listinfo/fpc-pascal
[fpc-pascal] Re: RE : Re: RE : Re: RE : FPCUp FPC/Lazarus installer/updater: first Linux/Windows version released
On 11-2-2012 10:30, Ludo Brands wrote: > One other problem: the debugger is configured as gdb which is not working. > Lazarus looks for a gdb in the current directory (whatever that is), not in > the path. Using the output of 'which gdb' would be the easiest solution on > linux to set up the default gdb. Just committed running 'which' to get gdb path for Unix/Linux. Not yet tested (or compiled, TBH). ___ fpc-pascal maillist - fpc-pascal@lists.freepascal.org http://lists.freepascal.org/mailman/listinfo/fpc-pascal
Re: [fpc-pascal] Re: RE : Re: RE : FPCUp FPC/Lazarus installer/updater: first Linux/Windows version released
Reinier Olislagers hat am 11. Februar 2012 um 08:28 geschrieben: > On 10-2-2012 18:23, Ludo Brands wrote: > >>> - (I hesitated to put this in the category "bugs") lazarus is > >>> configured to use (default on ubuntu) ~/fpc/bin/fpc. I have 2.4.4 > >>> installed with a /etc/fpc.cfg and ~/fpc/bin/fpc will just launch > >>> 2.4.4. Changing the compiler to ~/fpc/compiler/ppc386 and copying > >>> fpc.cfg to ~/fpc/compiler/ still fails because the compiler still > >>> picks up /etc/fpc.cfg. AFAIK the fpc.cfg in the compiler > >> dir will only > >>> be picked up when there is no .fpc.cfg in the home directory nor a > >>> fpc.cfg in the current directory nor one in the path specified by > >>> PPC_CONFIG_PATH nor a /etc/fpc.cfg. Detecting a conflicting fpc.cfg > >>> and warning the user would be nice. > >> Agreed. > >> If I understand the FPC User's Guide correctly, one could use > >> the -n option to tell fpc to ignore config files, then > >> specify the one we want with @. The question is, can that be > >> done with Lazarus Project Options / Compiler Options / Other - I suppose not... Why do you think so? >Would copying over the > >> newly installed FPC compiler's fpc.cfg to the installed > >> lazarus dir work? > >> > > > > I tried the latter but it didn't work. > What about letting fpcup write another shell script for fpc e.g. > something like: > > #!/bin/sh > ~/wherever/we/installed/fpc -n @~/wherever/we/installed/fpc.cfg $* > which should instruct our fpc to ignore any other fpc.cfg, use our own, > and get any other arguments passed to the script. > > Then assign this script as the compiler in Lazarus?!?! No need. > > (I suppose this might not work as Lazarus might be looking for other > files in the compiler path!??!) Lazarus does neither read nor search the fpc.cfg. It asks the compiler. Mattias ___ fpc-pascal maillist - fpc-pascal@lists.freepascal.org http://lists.freepascal.org/mailman/listinfo/fpc-pascal
RE : [fpc-pascal] Re: RE : Re: RE : Re: RE : FPCUp FPC/Lazarus installer/updater: first Linux/Windows version released
> > It picks up the right compiler but there is still a problem though: > > fpc.cfg includes the units searchpath > > ~/wherever/we/installed/units/$fpctarget but make install > > INSTALL_PREFIX=blah installs in > > blah/lib/fpc/$fpcversion/units/$fpctarget. Running 'fpcmkcfg -d > > basepath=~/wherever/we/installed/lib/fpc/2.6.1 ...' solves this. > > Unfortunately > 'basepath=~/wherever/we/installed/lib/fpc/$fpcversion' > > doesn't work. Lazarus seems to be perfectly happy with the > script (I > > installed it in the fpc/bin directory) > > Ok, I've added this to my todo list > http://lazarus.freepascal.org/index.php/topic,15919.0.html > In the meantime, patches welcome :) > Patch for script, unit path (using INSTALL_UNITDIR make parameter) and gdb/make attached. Ludo fpcup.diff Description: Binary data ___ fpc-pascal maillist - fpc-pascal@lists.freepascal.org http://lists.freepascal.org/mailman/listinfo/fpc-pascal
Re: RE : [fpc-pascal] Re: RE : Re: RE : FPCUp FPC/Lazarus installer/updater: first Linux/Windows version released
On 11.02.2012 10:30, Ludo Brands wrote: #!/bin/sh ~/wherever/we/installed/fpc -n @~/wherever/we/installed/fpc.cfg $* which should instruct our fpc to ignore any other fpc.cfg, use our own, and get any other arguments passed to the script. Then assign this script as the compiler in Lazarus?!?! (I suppose this might not work as Lazarus might be looking for other files in the compiler path!??!) The script still picks up 2.4.4 but the idea is good. This works: #!/bin/sh ~/wherever/we/installed/compiler/ppc386 -n @~/wherever/we/installed/fpc.cfg $* You can use the "-Xp" option to specify a path for FPC to search for the ppc* binaries. E.g. #!/bin/sh ~/whereever/we/installed/fpc -n @~/whereever/we/installed/fpc.cfg -Xp~/whereever/we/installed/compiler $* Regards, Sven ___ fpc-pascal maillist - fpc-pascal@lists.freepascal.org http://lists.freepascal.org/mailman/listinfo/fpc-pascal
Re: [fpc-pascal] Re: RE : Re: RE : FPCUp FPC/Lazarus installer/updater: first Linux/Windows version released
On 11-2-2012 13:15, Mattias Gaertner wrote: > > Reinier Olislagers hat am 11. Februar 2012 > um 08:28 geschrieben: >> On 10-2-2012 18:23, Ludo Brands wrote: >> >>> - (I hesitated to put this in the category "bugs") lazarus is >> >>> configured to use (default on ubuntu) ~/fpc/bin/fpc. I have 2.4.4 >> >>> installed with a /etc/fpc.cfg and ~/fpc/bin/fpc will just launch >> >>> 2.4.4. Changing the compiler to ~/fpc/compiler/ppc386 and copying >> >>> fpc.cfg to ~/fpc/compiler/ still fails because the compiler still >> >>> picks up /etc/fpc.cfg. AFAIK the fpc.cfg in the compiler >> >> dir will only >> >>> be picked up when there is no .fpc.cfg in the home directory nor a >> >>> fpc.cfg in the current directory nor one in the path specified by >> >>> PPC_CONFIG_PATH nor a /etc/fpc.cfg. Detecting a conflicting fpc.cfg >> >>> and warning the user would be nice. >> >> Agreed. >> >> If I understand the FPC User's Guide correctly, one could use >> >> the -n option to tell fpc to ignore config files, then >> >> specify the one we want with @. The question is, can that be >> >> done with Lazarus > Project Options / Compiler Options / Other Danke, Mattias... The thing is, we would like to set that by default, and also, if possible, let lazbuild work with it... I suppose we could write some default value for Project Options/Compiler Options/Other but that would lead to problems whenever the user opens projects from another computer or even his side-by-side Lazarus install... >> #!/bin/sh >> ~/wherever/we/installed/fpc -n @~/wherever/we/installed/fpc.cfg $* >> which should instruct our fpc to ignore any other fpc.cfg, use our own, >> and get any other arguments passed to the script. >> >> Then assign this script as the compiler in Lazarus?!?! > No need. > >> > (I suppose this might not work as Lazarus might be looking for other >> files in the compiler path!??!) > > Lazarus does neither read nor search the fpc.cfg. It asks the compiler. Correct. Calling our newly installed fpc will presumably show the same problems (e.g. loading /etc/fpc.cfg) if a system-wide fpc was already installed A shell script in e.g. the user's home directory seems like a valid solution, but I'm open to suggestions... Regards, Reinier ___ fpc-pascal maillist - fpc-pascal@lists.freepascal.org http://lists.freepascal.org/mailman/listinfo/fpc-pascal
RE : [fpc-pascal] Re: RE : Re: RE : Re: RE : FPCUp FPC/Lazarus installer/updater: first Linux/Windows version released
> > Regarding side by side installations, wouldn't it be better > to store > > the lazarus config in a subdir of the lazarus install? A fixed > > directory makes side by side installation of lazarus very difficult. > You mean a --primary-config path underneath the lazarus > application directory? Could be done in principle. > > Then again, current fpcup does not have a fixed > primary-config-path, merely a default one. > Unless I overlooked something, the primary-config-path is pretty hardcoded now (XdgConfigHome/lazarusdevsettings). Adding a parameter for primary-config-path would solve a lot. > I intended to leave the fpc and lazarus svn directories alone > as much as possible so a user could delete everything and do > a new checkout whenever he wants without touching config files. > Lazarus config files are sometimes part of the problem when working with svn. Making an all clean start would preferably also mean removing the lazarus config files. > I realize storing fpcup config files (e.g. SVN urls, etc) in > the lazarus and/or fpc svn dirs may not be desirable - if we > follow that strategy. > Why not create a fpcup script or link alongside the launcher(s) that take the same parameters as the one use to create the launcher? Something like 'lazlinkname' and 'lazlinkname Update'. Ludo > An alternative could be to use an fpcup config file stored > wherever config files are stored on the os (forgot the > function in FPC). Then use a default profile and allow the > user to add profiles (e.g. using --saveasprofile=bla). User > can invoke with --profile=bla. This will allow the GUI to > also easily retrieve a list of side-by-side installs... > > Regards, > Reinier > ___ > fpc-pascal maillist - fpc-pascal@lists.freepascal.org > http://lists.freepascal.org/mailman/listinfo/fpc-pascal > ___ fpc-pascal maillist - fpc-pascal@lists.freepascal.org http://lists.freepascal.org/mailman/listinfo/fpc-pascal
[fpc-pascal] Re: RE : Re: RE : Re: RE : Re: RE : FPCUp FPC/Lazarus installer/updater: first Linux/Windows version released
On 11-2-2012 14:19, Ludo Brands wrote: >>> Regarding side by side installations, wouldn't it be better >> to store >>> the lazarus config in a subdir of the lazarus install? A fixed >>> directory makes side by side installation of lazarus very difficult. >> You mean a --primary-config path underneath the lazarus >> application directory? Could be done in principle. >> >> Then again, current fpcup does not have a fixed >> primary-config-path, merely a default one. > Unless I overlooked something, the primary-config-path is pretty hardcoded > now (XdgConfigHome/lazarusdevsettings). Adding a parameter for > primary-config-path would solve a lot. Oops, yes, you're right; will do that. > Lazarus config files are sometimes part of the problem when working with > svn. Making an all clean start would preferably also mean removing the > lazarus config files. True, I think you just about persuaded me ;) >> I realize storing fpcup config files (e.g. SVN urls, etc) in >> the lazarus and/or fpc svn dirs may not be desirable - if we >> follow that strategy. > Why not create a fpcup script or link alongside the launcher(s) that take > the same parameters as the one use to create the launcher? Something like > 'lazlinkname' and 'lazlinkname Update'. Mmm, don't get what you mean here. What do you mean by launcher and the parameters used to create the launcher? Off working on making --primary-config-path configurable... and applying your patch... ___ fpc-pascal maillist - fpc-pascal@lists.freepascal.org http://lists.freepascal.org/mailman/listinfo/fpc-pascal
Re: RE : [fpc-pascal] Re: RE : Re: RE : Re: RE : FPCUp FPC/Lazarus installer/updater: first Linux/Windows version released
In our previous episode, Ludo Brands said: > > Then again, current fpcup does not have a fixed > > primary-config-path, merely a default one. > > > > Unless I overlooked something, the primary-config-path is pretty hardcoded > now (XdgConfigHome/lazarusdevsettings). Adding a parameter for > primary-config-path would solve a lot. There is --primary-config-path= and --lazarus-dir= the latter only with .30 iirc. I used these for stick installs, where driveletters could be different all the time. > Lazarus config files are sometimes part of the problem when working with > svn. Making an all clean start would preferably also mean removing the > lazarus config files. Daily going through the config dialogues is not fun either. ___ fpc-pascal maillist - fpc-pascal@lists.freepascal.org http://lists.freepascal.org/mailman/listinfo/fpc-pascal
RE : [fpc-pascal] Re: RE : Re: RE : Re: RE : Re: RE : FPCUp FPC/Lazarus installer/updater: first Linux/Windows version released
> > Why not create a fpcup script or link alongside the > launcher(s) that > > take the same parameters as the one use to create the > launcher? Something like > > 'lazlinkname' and 'lazlinkname Update'. > Mmm, don't get what you mean here. What do you mean by > launcher and the parameters used to create the launcher? > Sorry, I mean the shortcut on desktop or home dir. The parameters are the fpcup parameters used to do all the nice work and that finishes with the creation of the mentioned shortcut. So, the alternative to storing config parameters somewhere is the suggestion to not create one but 2 shortcuts. The first launches lazarus and the second launches fpcup with the same parameters that were used to create these links. Example: a side by side installation of lazarus fpc 2.6.1 and lazarus fpc 2.7.1 gives 4 shortcuts, lazarus2.6.1 , lazarus2.6.1(Update), lazarus2.7.1 and lazarus2.7.1(Update). Ludo ___ fpc-pascal maillist - fpc-pascal@lists.freepascal.org http://lists.freepascal.org/mailman/listinfo/fpc-pascal
[fpc-pascal] Re: RE : Re: RE : Re: RE : Re: RE : Re: RE : FPCUp FPC/Lazarus installer/updater: first Linux/Windows version released
On 11-2-2012 14:42, Ludo Brands wrote: > >>> Why not create a fpcup script or link alongside the >> launcher(s) that >>> take the same parameters as the one use to create the >> launcher? Something like >>> 'lazlinkname' and 'lazlinkname Update'. >> Mmm, don't get what you mean here. What do you mean by >> launcher and the parameters used to create the launcher? >> > Sorry, I mean the shortcut on desktop or home dir. The parameters are the > fpcup parameters used to do all the nice work and that finishes with the > creation of the mentioned shortcut. So, the alternative to storing config > parameters somewhere is the suggestion to not create one but 2 shortcuts. > The first launches lazarus and the second launches fpcup with the same > parameters that were used to create these links. Example: a side by side > installation of lazarus fpc 2.6.1 and lazarus fpc 2.7.1 gives 4 shortcuts, > lazarus2.6.1 , lazarus2.6.1(Update), lazarus2.7.1 and lazarus2.7.1(Update). > > Oh, I see. That would be possible and quite... orthogonal (isn't there a less stuffy word for this?) to any decisions on config files and where to store them... First let me get your patch and the --primary-config-path stuff done ;) Thanks, Reinier ___ fpc-pascal maillist - fpc-pascal@lists.freepascal.org http://lists.freepascal.org/mailman/listinfo/fpc-pascal
[fpc-pascal] Re: RE : Re: RE : Re: RE : Re: RE : FPCUp FPC/Lazarus installer/updater: first Linux/Windows version released
On 11-2-2012 14:32, Marco van de Voort wrote: > In our previous episode, Ludo Brands said: >>> Then again, current fpcup does not have a fixed >>> primary-config-path, merely a default one. >>> >> >> Unless I overlooked something, the primary-config-path is pretty hardcoded >> now (XdgConfigHome/lazarusdevsettings). Adding a parameter for >> primary-config-path would solve a lot. > > There is --primary-config-path= and --lazarus-dir= > > the latter only with .30 iirc. I used these for stick installs, where > driveletters could be different all the time. Thanks. As far as I can tell fpcup has no problem starting lazarus with the proper Lazarus directory but I might be missing something obvious again (happens a lot the last couple of days). Mmm, of course it could be useful when doing an install on a memory stick on Windows... yet another batch script to start lazarus I suppose ;) >> Lazarus config files are sometimes part of the problem when working with >> svn. Making an all clean start would preferably also mean removing the >> lazarus config files. > > Daily going through the config dialogues is not fun either. Mmm yes, but doing an svn up+compile on the lazarus dir, which fpcup does, shouldn't touch a --primary-config-path subdirectory (e.g. /LazarusDevSettings)... right? For now, I'll create a command line parameter --primary-config-path= that allows users to store the path wherever they wish and for now let it default to the situation it currently is (e.g. somewhere below ~ on Unix, somewhere below %localappdata% on Windows). ___ fpc-pascal maillist - fpc-pascal@lists.freepascal.org http://lists.freepascal.org/mailman/listinfo/fpc-pascal
RE : RE : [fpc-pascal] Re: RE : Re: RE : Re: RE : FPCUpFPC/Lazarus installer/updater: first Linux/Windows version released
> > Lazarus config files are sometimes part of the problem when working > > with svn. Making an all clean start would preferably also mean > > removing the lazarus config files. > > Daily going through the config dialogues is not fun either. > This was the case where the complete directory structure is deleted. Tabula rasa: full svn checkout, new fpc.cfg. Ludo ___ fpc-pascal maillist - fpc-pascal@lists.freepascal.org http://lists.freepascal.org/mailman/listinfo/fpc-pascal
[fpc-pascal] Re: RE : Re: RE : Re: RE : Re: RE : FPCUp FPC/Lazarus installer/updater: first Linux/Windows version released
On 11-2-2012 14:19, Ludo Brands wrote: >>> Regarding side by side installations, wouldn't it be better >> to store >>> the lazarus config in a subdir of the lazarus install? A fixed >>> directory makes side by side installation of lazarus very difficult. >> You mean a --primary-config path underneath the lazarus >> application directory? Could be done in principle. >> >> Then again, current fpcup does not have a fixed >> primary-config-path, merely a default one. > > Unless I overlooked something, the primary-config-path is pretty hardcoded > now (XdgConfigHome/lazarusdevsettings). Adding a parameter for > primary-config-path would solve a lot. I just committed a version with configurable --primary-config-path parameter. If not specified or empty, the original behavious still applies (eg. somewher below %localappdata% on windows, somewhere below ~ on Unix). Also committed your Unix unit= fix for FPC make, and fpc.sh launcher script creation. Thanks. Have not compiled in or tested on Linux though. Thanks, Reinier ___ fpc-pascal maillist - fpc-pascal@lists.freepascal.org http://lists.freepascal.org/mailman/listinfo/fpc-pascal
Re: [fpc-pascal] Re: TLinkedList
On Fri, Feb 10, 2012 at 17:53, leledumbo wrote: > I don't remember having that since 2.X.X... there was always TList, > however. > And that's what I was using (I use generics for all my containers use now). > Thanks. Personally I dislike generics at all. They are not that readable imho. Even though FPC's implementation is one of the most readable ways I have ever seen. Ido > > -- > View this message in context: > http://free-pascal-general.1045716.n5.nabble.com/TLinkedList-tp5469685p5472934.html > Sent from the Free Pascal - General mailing list archive at Nabble.com. > ___ > fpc-pascal maillist - fpc-pascal@lists.freepascal.org > http://lists.freepascal.org/mailman/listinfo/fpc-pascal > ___ fpc-pascal maillist - fpc-pascal@lists.freepascal.org http://lists.freepascal.org/mailman/listinfo/fpc-pascal
Re: [fpc-pascal] Re: TLinkedList
I believe generics makes faster code due to having no need to test types during runtime... i maybe wrong. 2012/2/11 ik : > On Fri, Feb 10, 2012 at 17:53, leledumbo wrote: >> >> I don't remember having that since 2.X.X... there was always TList, >> however. >> And that's what I was using (I use generics for all my containers use >> now). > > > Thanks. Personally I dislike generics at all. They are not that readable > imho. Even though FPC's implementation is one of the most readable ways I > have ever seen. > > Ido >> >> >> -- >> View this message in context: >> http://free-pascal-general.1045716.n5.nabble.com/TLinkedList-tp5469685p5472934.html >> Sent from the Free Pascal - General mailing list archive at Nabble.com. >> ___ >> fpc-pascal maillist - fpc-pascal@lists.freepascal.org >> http://lists.freepascal.org/mailman/listinfo/fpc-pascal > > > > ___ > fpc-pascal maillist - fpc-pascal@lists.freepascal.org > http://lists.freepascal.org/mailman/listinfo/fpc-pascal ___ fpc-pascal maillist - fpc-pascal@lists.freepascal.org http://lists.freepascal.org/mailman/listinfo/fpc-pascal
[fpc-pascal] Re: Adding Notes in FPDoc
On 11-2-2012 20:35, Michael Van Canneyt wrote: > On Sat, 11 Feb 2012, Howard Page-Clark wrote: >> The prospect of a website dedicated to discussion of documentation >> seems to me to be a helpful move forward. > It's not really about discussion (fed up with that, if you can believe > it ;) ), but about showing and collaborative editing of the docs. > The idea was/is the following: > > * All nodes of an FPDoc description file can be put in a database; > One record per element/module/whatnot, fields for short/descr/seealso > and whatnot elements. > I have the structure floating around here somewhere. > > * FPDoc needs (or already has, don't remember?) a mode to generate a > single HTML page, > based on node name. > > * The website can use the fpdoc engine to fetch and display the HTML > 'on-demand'. > > * For people with enough rights, the content can be edited. > > * When creating the full docs, the XML is read from the database and > written to an FPDoc file. > > In fact, not so different from a WIKI, but more structured. > > And now: > Since we now have notes, these can be displayed, and edited by all. I'd say go for it, Michael. If discussion can't be done in those notes, they can be done in some pages of the regular wiki with hyperlinks to the help HTML pages... Actually that is possible right now, I suppose ;) Regards, Reinier ___ fpc-pascal maillist - fpc-pascal@lists.freepascal.org http://lists.freepascal.org/mailman/listinfo/fpc-pascal
Re: [fpc-pascal] FPCUp FPC/Lazarus installer/updater: first Linux/Windows version released
Am Friday 10 February 2012 15:24:11 schrieb Reinier Olislagers: > Hi all, > > With the help of the people on the forums and the lists, I've completed > the first version of FPCup, a tool that downloads FPC and Lazarus > sources from SVN, compiles and installs them. Sorry for not reading the whole thread. But is it then also possible to povide a binary version of each (Linux) distro for easiest installing (just unzip the archive)? FPC and Lazarus in one sub directory? ___ fpc-pascal maillist - fpc-pascal@lists.freepascal.org http://lists.freepascal.org/mailman/listinfo/fpc-pascal
[fpc-pascal] Re: FPCUp FPC/Lazarus installer/updater: first Linux/Windows version released
On 11-2-2012 22:05, Rainer Stratmann wrote: > Sorry for not reading the whole thread. > But is it then also possible to povide a binary version of each (Linux) > distro > for easiest installing (just unzip the archive)? FPC and Lazarus in one sub > directory? fpcup downloads (or updates) and installs fpc+lazarus and compiles them+adds some shortcuts/shell scripts that start up the new Lazarus. Both the newly installed FPC and Lazarus could reside in the same directory or at least subdirectories eg: ~ \ trunk | +-Lazarus +-fpc You'd need to provide the suitable directories to fpcup in the command line (see fpcup --help). A GUI for all of this is in development. While the point of the program is to provide developers with an up to date version of SVN trunk (or whichever SVN branch/tag you want to track), it does not install documentation etc at the moment, or provide for a binary install (without downloading sources from SVN), and I think the .deb and .rpm packages are more suitable for that. However, the desired goal of the program is that you run it and just get a working SVN version of Lazarus and FPC. I suggest you try it on your Linux distro and see what happens. It is designed to leave any existing Lazarus and FPC installs alone (unless, of course, the installation directories overlap; see fpcup --help for options) If you encounter any bugs, I'd be happy to try and fix them. Regards, Reinier ___ fpc-pascal maillist - fpc-pascal@lists.freepascal.org http://lists.freepascal.org/mailman/listinfo/fpc-pascal
Re: [fpc-pascal] Re: TLinkedList
2012/2/11, Jorge Aldo G. de F. Junior : > I believe generics makes faster code due to having no need to test > types during runtime... i maybe wrong. It is true only if you use the type-safe "as" casting. Normal casting does not check types at runtime. It does make the code more readable. Like: MyVar := MyList[i]; compared to MyVar := TMyType(MyList[i]); Also, you get compile time type-checking, just like arrays had from day 1. The code is safer, more readable and self-documenting. I hope there will be a good and comprehensive generics container library. Now the containers are scattered around and are competing with each other. Java serves as a good example here. It has a consistent generics container library. Classes are easy to find and use. Juha ___ fpc-pascal maillist - fpc-pascal@lists.freepascal.org http://lists.freepascal.org/mailman/listinfo/fpc-pascal
