On Sun, Nov 9, 2014 at 4:51 PM, Tomas Hajny xhaj...@hajny.biz wrote:
I've finished implementation of solution for easier parsing of
supported values for certain options and the solution _does_ match
the compiler capabilities because the values come from the particular
compiler itself.
Thanks.
On Wed, November 12, 2014 13:03, Juha Manninen wrote:
On Sun, Nov 9, 2014 at 4:51 PM, Tomas Hajny xhaj...@hajny.biz wrote:
I've finished implementation of solution for easier parsing of
supported values for certain options and the solution _does_ match
the compiler capabilities because the
On Wed, Nov 12, 2014 at 7:03 AM, Juha Manninen juha.mannine...@gmail.com
wrote:
The fact still is that fpc -h + a parser in Lazarus requires the
least amount of maintenance in the long run.
The help output already listed the vast majority of all options.
Is there an exclusion for -P option
On 12 Nov 14, at 16:32, Dmitry Boyarintsev wrote:
On Wed, Nov 12, 2014 at 7:03 AM, Juha Manninen juha.mannine...@gmail.com
wrote:
The fact still is that fpc -h + a parser in Lazarus requires the
least amount of maintenance in the long run.
The help output already listed the vast
On Wed, Nov 12, 2014 at 11:32 PM, Dmitry Boyarintsev
skalogryz.li...@gmail.com wrote:
Is there an exclusion for -P option in the parser?
After all the flag make sense for fpc but not ppcXXX.
No but IMO it should be excluded from the user choices.
The parser calls the compiler with
On 13 Nov 14, at 0:20, Juha Manninen wrote:
On Wed, Nov 12, 2014 at 11:32 PM, Dmitry Boyarintsev
skalogryz.li...@gmail.com wrote:
Is there an exclusion for -P option in the parser?
After all the flag make sense for fpc but not ppcXXX.
No but IMO it should be excluded from the user
On 13 Nov 14, at 0:20, Juha Manninen wrote:
On Wed, Nov 12, 2014 at 11:32 PM, Dmitry Boyarintsev
skalogryz.li...@gmail.com wrote:
Is there an exclusion for -P option in the parser?
After all the flag make sense for fpc but not ppcXXX.
No but IMO it should be excluded from the user
On Sunday, November 9, 2014, Dmitry Boyarintsev skalogryz.li...@gmail.com
wrote:
On Sat, Nov 8, 2014 at 2:15 PM, Juha Manninen juha.mannine...@gmail.com
javascript:_e(%7B%7D,'cvml','juha.mannine...@gmail.com'); wrote:
On Fri, Nov 7, 2014 at 1:13 AM, Tomas Hajny xhaj...@hajny.biz
On Sunday, November 9, 2014, Dmitry Boyarintsev skalogryz.li...@gmail.com
wrote:
Pardon me, but I actually opposed the idea to put any kind of changes to
FPC help system.
My reasoning - it would be an additional and annoying burden to fpc-team.
As bug reports showing, help is not in sync with
On Sun, Nov 9, 2014 at 4:27 AM, Juha Manninen juha.mannine...@gmail.com
wrote:
Sorry, my bad. We had a long discussion about this subject, Mattias
thought the info about FPC options should be maintained in FPC project. I
agreed because it is quite logical and makes sense. Why should help info
On 9 Nov 14, at 9:15, Dmitry Boyarintsev wrote:
On Sun, Nov 9, 2014 at 4:27 AM, Juha Manninen juha.mannine...@gmail.com
wrote:
Sorry, my bad. We had a long discussion about this subject, Mattias
thought the info about FPC options should be maintained in FPC project. I
agreed because it
On Fri, Nov 7, 2014 at 1:13 AM, Tomas Hajny xhaj...@hajny.biz wrote:
If you mean that FPC itself should use a JSON file for generating the
help, that doesn't sound like a good idea to me (see below).
I think it is a good idea if only somebody implemented it. It is not a
trivial thing to
On 8 Nov 14, at 12:15, Juha Manninen wrote:
On Fri, Nov 7, 2014 at 1:13 AM, Tomas Hajny xhaj...@hajny.biz wrote:
If you mean that FPC itself should use a JSON file for generating the
help, that doesn't sound like a good idea to me (see below).
I think it is a good idea if only somebody
On Sat, Nov 8, 2014 at 2:15 PM, Juha Manninen juha.mannine...@gmail.com
wrote:
On Fri, Nov 7, 2014 at 1:13 AM, Tomas Hajny xhaj...@hajny.biz wrote:
If you mean that FPC itself should use a JSON file for generating the
help, that doesn't sound like a good idea to me (see below).
I think it
Lazarus has a GUI for all FPC options, parsed directly from fpc -h
and fpc -i.
Project Options - Compiler Options - Other - All Options ...
It was temporarily broken with FPC trunk but works now.
I had to hard-code some things in the parser because fpc -h output
does not give enough data.
1.
On Thu, November 6, 2014 23:30, Juha Manninen wrote:
Lazarus has a GUI for all FPC options, parsed directly from fpc -h
and fpc -i.
Project Options - Compiler Options - Other - All Options ...
.
.
fpc -h output would be generated from the JSON data, thus it would
not require more
16 matches
Mail list logo
