I'm suspecting that there are hints sometimes that aren't shown all the time. I
just made a change, and it showed a hint when I hit F9. Then, having had the
suspicion, I hit F9 again, and it recompiled and no hints. There appears to be no
way to do a "build", only a compile, so I'm not sure what is happening. Maybe the
hint went away really, but I post here in case it triggers a thought in someone
else.

/Matthew Jones/

Positive sighting! I got a hint about an unused local variable. Went to the
location. Hit F9, no hints again. Okay, slight edit, no hints. Comment the line out
and compile, no hint (expected). Uncomment the line to put the unused variable back,
compile, hint appears. Compile again, hint disappears.

It is quite minor, but worth logging.

/Matthew Jones/

>>Positive sighting! I got a hint about an unused local variable. Went to the
>>location. Hit F9, no hints again

I have also noticed this from time to time. I had thought that a compile only looks at files that have changed since the last compile. Therefore, if you modify a file that contains some "hintable" code, the next compile will show the hint. A subsequent compile will not (since the file has not be changed). In fact, the hint will not resurface until the containing file is changed again.

Matthew,

<< It is quite minor, but worth logging. >>

As Mark indicated, it's not a bug - the compiler will only recompile source
units that have changed, so if you haven't change the source code, then a
re-compile will no longer show any hints for that unit.

Tim Young
Elevate Software
www.elevatesoft.com

Changing the file doesn't seem to do it, but changing the code does. Not sure how
it knows the difference. In Delphi, you have compile and you have build. The latter
ensures all files are compiled and shows hints and warnings.

/Matthew Jones/

Can I suggest a "trivial issues" topic on the newsgroups? A lot of these things I'm
finding don't warrant a public discussion in an otherwise useful topic. They may
look like 100 faults, when they are no more than any other software product.

Anyway, the help for MessageDlg has a trivial error - no closing quote on the first
line. I just pasted it into my code and saw it...

MessageDlg('Are you sure that you want to delete this record?,
          'Please Confirm',mtConfirmation,[mbYes,mbNo],mbNo,CheckDelete,True);

/Matthew Jones/

On 13/06/13 21:16, (Matthew Jones) wrote:
> Can I suggest a "trivial issues" topic on the newsgroups? A lot of these things I'm
> finding don't warrant a public discussion in an otherwise useful topic. They may
> look like 100 faults, when they are no more than any other software product.
>
> Anyway, the help for MessageDlg has a trivial error - no closing quote on the first
> line. I just pasted it into my code and saw it...
>
> MessageDlg('Are you sure that you want to delete this record?,
>             'Please Confirm',mtConfirmation,[mbYes,mbNo],mbNo,CheckDelete,True);
>
> /Matthew Jones/
>
I agree that issues no matter how trivial should be reported. Even
seemingly small problems like documentation errors are worth fixing.

Maybe it would be worth opening an incident record using the form
provided on the Elevate Software Web site. Just mark it as a minor
incident. I've raised a couple of those and even though I haven't seen
them appear in the report yet I'd guess that having them recorded
probably helps with support.

EWB is a very good piece of software, rapidly becoming indispensable.
Who knows, these forums may soon be flooded with posts from interested
developers making it difficult for Tim to notice any issues raised.


--
Rick

Another trivial one - you can do:

case myValue of
4: DoSomething;
4: DoOther;
end;

It may be nice to compile time check the cases are unique.

/Matthew Jones/

I have sent a few via the incident form - a good idea.

/Matthew Jones/

Matthew,

<< Can I suggest a "trivial issues" topic on the newsgroups? A lot of these
things I'm finding don't warrant a public discussion in an otherwise useful
topic. They may look like 100 faults, when they are no more than any other
software product. >>

I don't think it matters too much.  However, documentation errors you can
just fire off to me - they don't warrant a response usually and are easily
corrected.

Thanks,

Tim Young
Elevate Software
www.elevatesoft.com