Alexander Klenin escreveu:
> On Sat, Apr 11, 2009 at 22:39, Luiz Americo Pereira Camara
> wrote:
>
>> Alexander Klenin escreveu:
>>
>
>
>>> OTOH, the hint is not _entirely_ useless and can in some rare cases
>>> point to a real bugs.
>>> The solution is to enable per-variable hint suppr
On Sat, Apr 11, 2009 at 22:39, Luiz Americo Pereira Camara
wrote:
> Alexander Klenin escreveu:
>> OTOH, the hint is not _entirely_ useless and can in some rare cases
>> point to a real bugs.
>> The solution is to enable per-variable hint suppression. It is done in C/C++
>> by omitting variable na
Alexander Klenin wrote:
> On Sat, Apr 11, 2009 at 07:53, Alexander Klenin wrote:
>> On Sat, Apr 11, 2009 at 07:17, Christian Iversen
>> wrote:
>>> Ok, I can see what you're doing there. In my opinion, it's not very
>>> pretty. How about something like this:
>>>
>>> procedure SilenceHint(const A);
Luiz Americo Pereira Camara wrote:
> Are you aware that fpc trunk already implemented an option to disable hints?
>
> See: http://bugs.freepascal.org/view.php?id=8690
>
Lazarus trunk also has this options.
Best regards,
Paul Ishenin.
___
Lazarus maili
Hello Joost,
Saturday, April 11, 2009, 11:48:02 AM, you wrote:
JvdS> Very nice that you have made up this rule for yourself. But as you've
JvdS> find out you really make things complicated for yourself.
[...]
JvdS> And there are 'hints', things which are things that the compiler finds
JvdS> suspi
Alexander Klenin escreveu:
> 2009/4/9 Mattias Gärtner :
>
>>> As I already written some time ago, the solution is to introduce a
>>> hint/warning for the circular dependencies in implementation sections.
>>> This hint should probably be disabled by default, for compatibility reasons.
>>>
Op vrijdag 10-04-2009 om 22:51 uur [tijdzone +0200], schreef JoshyFun:
> Friday, April 10, 2009, 10:17:28 PM, you wrote:
>
> >> In other words MY (capital, as it is my problem, maybe not the problem
> >> of other people) is that the amount of expected hints are hidding the
> >> non-expected ones.
Hello Vincent,
Friday, April 10, 2009, 10:31:19 PM, you wrote:
VS> Christian Iversen schreef:
>>
>> SilenceHint(Sender, X, Y);
>>
VS> Or use array of const, like the format function.
H... array of const does not use variants so it could be fine, in
spanish keyboard the combination is quite
On Sat, Apr 11, 2009 at 07:53, Alexander Klenin wrote:
> On Sat, Apr 11, 2009 at 07:17, Christian Iversen
> wrote:
>> Ok, I can see what you're doing there. In my opinion, it's not very
>> pretty. How about something like this:
>>
>> procedure SilenceHint(const A); inline;
>> begin
>> end;
BTW,
On Sat, Apr 11, 2009 at 07:17, Christian Iversen
wrote:
> Ok, I can see what you're doing there. In my opinion, it's not very
> pretty. How about something like this:
>
> procedure SilenceHint(const A); inline;
> begin
> end;
I still prefer compiler-level solution, but if Lazarus team agrees,
I c
Hello Christian,
Friday, April 10, 2009, 10:17:28 PM, you wrote:
>> In other words MY (capital, as it is my problem, maybe not the problem
>> of other people) is that the amount of expected hints are hidding the
>> non-expected ones.
CI> Right. And as I said, it would probably be more productive
Christian Iversen schreef:
>
> SilenceHint(Sender, X, Y);
>
Or use array of const, like the format function.
Vincent
___
Lazarus mailing list
Lazarus@lazarus.freepascal.org
http://www.lazarus.freepascal.org/mailman/listinfo/lazarus
JoshyFun wrote:
> Hello Christian,
>
> Friday, April 10, 2009, 1:20:43 AM, you wrote:
>
> CI> That's really 2 statements:
> CI> A) There should be a way to tell the compiler that the hint is expected
> CI> Well, I can't see why this is a given. By definition, hints are things
> CI> that _can_ be
Hello Christian,
Friday, April 10, 2009, 1:20:43 AM, you wrote:
CI> That's really 2 statements:
CI> A) There should be a way to tell the compiler that the hint is expected
CI> Well, I can't see why this is a given. By definition, hints are things
CI> that _can_ be potentially dangerous, but it's
JoshyFun wrote:
> Hello Christian,
>
> Thursday, April 9, 2009, 7:13:06 PM, you wrote:
>
> CI> Hint: Something that can't be ruled out as dangerous, but might just be.
> CI> For practical reasons, this category can't be merged with "warnings",
> CI> because that would then produce so many warning
Hello Christian,
Thursday, April 9, 2009, 7:13:06 PM, you wrote:
CI> Hint: Something that can't be ruled out as dangerous, but might just be.
CI> For practical reasons, this category can't be merged with "warnings",
CI> because that would then produce so many warnings that the only useful
CI> err
Alexander Klenin wrote:
> [...]
> 2) The compiler produces _many_ extraneous hints, which is very harmful --
> it is impossible to produce hints-free code, so new hints has much
> more chances to go unnoticed.
While I agree in principle that extra verbosity is a source of bugs, the
"hint" s
Zitat von Alexander Klenin :
> 2009/4/9 Mattias Gärtner :
> >> As I already written some time ago, the solution is to introduce a
> >> hint/warning for the circular dependencies in implementation sections.
> >> This hint should probably be disabled by default, for compatibility
> reasons.
> >
> >
2009/4/9 Mattias Gärtner :
>> As I already written some time ago, the solution is to introduce a
>> hint/warning for the circular dependencies in implementation sections.
>> This hint should probably be disabled by default, for compatibility reasons.
>
> Yes, a hint would be nice.
> But a hint won'
19 matches
Mail list logo
