Re: [fpc-pascal] Codetools and C-style constructs
Am 18.12.2012 23:56, schrieb Mattias Gaertner: On Tue, 18 Dec 2012 21:13:22 + Howard Page-Clark wrote: Looking through some of the codetools sources makes me wonder if the codetools overlooks some C-style FPC operators. KeywordFuncLists.pas, for instance, seems not to know about >>, <<, +=, -=, *=, /=. I added the << and >>. The others are assignment operators. AFAIK they can not be overloaded. Note: "<<" and ">>" are handled by FPC's scanner, so they are exactly the same as "shl" and "shr" The others can be overloaded insofar that the baseoperator is used as the C-style assignment operators are simply expanded by the parser (e.g. a += b becomes a := a + b and thus the "+" operator applies) Regards, Sven ___ fpc-pascal maillist - fpc-pascal@lists.freepascal.org http://lists.freepascal.org/mailman/listinfo/fpc-pascal
[fpc-pascal] Re: Documentation
On 18-12-2012 0:58, Graeme Geldenhuys wrote: > There are other issues with the FPDoc Editor dialog though. Off the top > of my head: As I think I said last year, there's also Laz DE/Lazarus Documentation Editor. As long as we're suggesting improvements, I'd like LazDE to 1. show a formatted view of the resulting fpdoc (i.e. use fpdoc processing to output as e.g. HTML and show that) so you have direct feedback on how your documentation looks. 2. use an XML syntax highlighter (synmemo?) (if it's not already there). Helps with those missing closing tags etc I suffer from 3. allow drag and drop from an identifier in a source code window to create a link automatically. 4. (from memory, haven't done this a while) make it easier to start documenting a new unit. Whenever I start, I have no idea what package name I should supply. Some automated suggestions might be nice. However, fpdoc documentation writing is a huge chore for me compared to writing in the wiki so I've decided it's more productive to get my documentation done on the wiki. I still have documentation for the zip unit lying around and I'm trying to get that in shape to submit it. Meanwhile I've updated the fpdoc code some with cosmetic changes/better warning messages: http://bugs.freepascal.org/view.php?id=23506 ... so if anybody is interested ;) Thanks, Reinier ___ fpc-pascal maillist - fpc-pascal@lists.freepascal.org http://lists.freepascal.org/mailman/listinfo/fpc-pascal
[fpc-pascal] Re: Documentation
On 18-12-2012 13:28, Marco van de Voort wrote: > In our previous episode, Reinier Olislagers said: >> However, fpdoc documentation writing is a huge chore for me compared to >> writing in the wiki so I've decided it's more productive to get my >> documentation done on the wiki. > > Wiki is not versioned, not context sensitive etc. It is a perfect place to > do some quick scribblings and howtos, but it is not a solution for final > documentation. You didn't understand what I was trying to say. See my response to Michael. That is the probably reaon why people are e.g. now documenting the entire Pascal list of reserved words on the wiki rather than in fpdoc. ___ fpc-pascal maillist - fpc-pascal@lists.freepascal.org http://lists.freepascal.org/mailman/listinfo/fpc-pascal
