Re: [fpc-pascal] List of chars for case

> So it can’t be done? Only through macro ATM, I believe. Note that case statement body does NOT expect a set (it expects values, list of values and/or range of values), despite the very similar look (missing enclosing angle brackets only), hence the inability to do what you want. -- Sent

Re: [fpc-pascal] Loss of precision when using math.Max()

On 07/02/18 15:13, Wolf wrote: Not so long ago, Florian was proudly bragging about "Pascal does not allow you to shoot yourself in the foot " What about this little program: program Project1; var a,b: byte; begin  

Re: [fpc-pascal] fpdoc error with XML parsing

On 07/02/18 21:28, wkitt...@windstream.net wrote: > can fpdoc process comments spanning multiple lines? Yes it can. That same XML file contains multi-line comments too, and those don't give issues. eg: ...snip... ...snip...

Re: [fpc-pascal] Loss of precision when using math.Max()

Not so long ago, Florian was proudly bragging about "Pascal does not allow you to shoot yourself in the foot " What about this little program: program Project1; var a,b: byte; begin   a:=1;   b:=a*(-1);   writeln(b);    //

Re: [fpc-pascal] fpdoc error with XML parsing

On 07/02/2018 04:11 PM, Graeme Geldenhuys wrote: What is illegal about this fpdoc XML project file? fpdoc from FPC 3.1.1 keeps giving an exception error reading the XML document. The issue it has is with the XML Comment I have on lines 2-5 (ignore the line wrapping caused by my email client). If

[fpc-pascal] fpdoc error with XML parsing

Hi, What is illegal about this fpdoc XML project file? fpdoc from FPC 3.1.1 keeps giving an exception error reading the XML document. The issue it has is with the XML Comment I have on lines 2-5 (ignore the line wrapping caused by my email client). If I remove that comment, then the XML is read,

Re: [fpc-pascal] TFPGObjectList error

On 07/01/18 23:16, Michael Van Canneyt wrote: Seems I forgot to update the symlink when we released. I fixed that. Thanks for pointing it out. No problem. I consider this an error in your reasoning. The bugtracker is very lowlevel, and should be usable and familiar for all. Many of

Re: [fpc-pascal] TFPGObjectList error

In our previous episode, Ryan Joseph said: > > > > And to what page would this script then point when you find something ? If > > it was easy, it would have been done already. > > > > But, here's your shot at contributing :) > > The easiest thing would be to read the .chm file and search that

Re: [fpc-pascal] TFPGObjectList error

On Mon, July 2, 2018 08:16, Michael Van Canneyt wrote: > On Sun, 1 Jul 2018, Jim Lee wrote: >> On 07/01/18 12:28, Michael Van Canneyt wrote: . . >> An auto-generated index of all identifiers used across all modules is >> useful, if you know what you're looking for.  Say I was looking for >>

Re: [fpc-pascal] TFPGObjectList error

> On Jul 2, 2018, at 5:39 AM, Michael Van Canneyt > wrote: > > I'm reviving my 'search docs' engine attempt. The idea is to create a single > index for all doc pages, which would be updated when the documentation is > regenerated. why can’t the .chm file be read on the server? There’s

Re: [fpc-pascal] TFPGObjectList error

> On Jul 1, 2018, at 11:55 PM, Michael Van Canneyt > wrote: > > And to what page would this script then point when you find something ? If it > was easy, it would have been done already. > > But, here's your shot at contributing :) The easiest thing would be to read the .chm file and

Re: [fpc-pascal] List of chars for case

> On Jul 2, 2018, at 2:07 AM, Mattias Gaertner > wrote: > > That would be useful. So it can’t be done? Regards, Ryan Joseph ___ fpc-pascal maillist - fpc-pascal@lists.freepascal.org

Re: [fpc-pascal] GetAppConfigDir(False) in a Citrix environment

On Fri, Jun 29, 2018 at 7:23 PM, Graeme Geldenhuys wrote: > Oh wow, talk about perfect timing. This afternoon I had to look into a > bug where our app also runs under a Citrix environment, and on reboot > (or new session) the settings are lost. @Graeme: did you manage to translate all that into

Re: [fpc-pascal] TFPGObjectList error

On Mon, Jul 2, 2018 at 3:16 AM, Michael Van Canneyt wrote: > > [...] > > Contrary to what it may seem it is not so easy to make a search engine for > the documentation. I've had several shots at it, but have not yet come up > with a good mechanism. The last mechanism I tried ended up indexing

Re: [fpc-pascal] TFPGObjectList error

On Mon, 2 Jul 2018, Marco van de Voort wrote: In our previous episode, Michael Van Canneyt said: It takes currently about 1000 secs to process the FCL docs (~ 5000 files). That seems acceptable to me. Test with the LCL docs. Generating a rtl or fcl chm is measured in tens of seconds, LCL

Re: [fpc-pascal] TFPGObjectList error

In our previous episode, Michael Van Canneyt said: > It takes currently about 1000 secs to process the FCL docs (~ 5000 files). > That seems acceptable to me. Test with the LCL docs. Generating a rtl or fcl chm is measured in tens of seconds, LCL a full 8 minutes.

Re: [fpc-pascal] TFPGObjectList error

On Mon, 2 Jul 2018, Martok wrote: Am 02.07.2018 um 11:46 schrieb Michael Van Canneyt: The CHM manual generation is as problematic as the indexing itself. And the CHM search index is generated by Windows on first use, as far as I know. Hm, okay. Not really helping then, sorry. They never

Re: [fpc-pascal] TFPGObjectList error

In our previous episode, Michael Van Canneyt said: > > > > From what it looks like, this is built on the CHM format files? If one could > > figure out what they use, maybe that would be a step in the right direction? > > The CHM manual generation is as problematic as the indexing itself. > And

Re: [fpc-pascal] TFPGObjectList error

Am 02.07.2018 um 11:46 schrieb Michael Van Canneyt: > The CHM manual generation is as problematic as the indexing itself. > And the CHM search index is generated by Windows on first use, as far as I > know. Hm, okay. Not really helping then, sorry. > They never were designed to be interlinked: >

Re: [fpc-pascal] TFPGObjectList error

On Mon, 2 Jul 2018, Martok wrote: Without a good search feature these are really hard to use. Searching should be the first priority. Can’t we just make a little script to put on the server which searches the original indexed format which the HTML is derived from? It would be so easy to

Re: [fpc-pascal] TFPGObjectList error

> Without a good search feature these are really hard to use. Searching should > be the first priority. Can’t we just make a little script to put on the > server which searches the original indexed format which the HTML is derived > from? It would be so easy to make something that’s cheap but

Re: [fpc-pascal] Loss of precision when using math.Max()

El 01/07/2018 a las 10:27, C Western escribió: On 29/06/18 21:55, Sven Barth via fpc-pascal wrote: More confusingly, if a single variable is used, the expected Max(Double, Double) is called: function Max(a, b: Double): Double; overload; begin   WriteLn('Double');   if a > b then Result := a

Re: [fpc-pascal] List of chars for case

On Sun, 1 Jul 2018 16:51:08 -0600 Ryan Joseph wrote: > Is there a way to make a constant for a list of chars which I can use in a > case statement? I’ve got a bunch of code duplication happening I’d like to > clean up. > > const > TChars = ('[', ']', '(', ')', '{', '}', '=', ‘:’); > > >

Re: [fpc-pascal] Loss of precision when using math.Max()

On 01/07/18 09:27, C Western wrote: On 29/06/18 21:55, Sven Barth via fpc-pascal wrote: Am 29.06.2018 um 18:45 schrieb Alan Krause: I stumbled upon something the other day that was causing numerical differences between compiled Delphi and FPC code. Executing the following sample console

Re: [fpc-pascal] List of chars for case

Ryan Joseph wrote: Is there a way to make a constant for a list of chars which I can use in a case statement? I’ve got a bunch of code duplication happening I’d like to clean up. const TChars = ('[', ']', '(', ')', '{', '}', '=', ‘:’); case c of TChars: ... Regards,

Re: [fpc-pascal] TFPGObjectList error

On Sun, 1 Jul 2018, Jim Lee wrote: On 07/01/18 12:28, Michael Van Canneyt wrote: The documentation is brought up to date at every release: all new identifiers are documented and the documentation regenerated. If you look in the bugtracker, you will see that I regularly fix documentation