Watch, Follow, &
Connect with Us
Public Report
Report From: Delphi-BCB/IDE/Structure Pane/Error Insight    [ Add a report in this area ]  
Report #:  57208   Status: Closed
Semicolon between function type and stdcall required for EI, optional for compiler
Project:  Delphi Build #:  all
Version:    11.2 Submitted By:   Alexey Rytov
Report Type:  Minor failure / Design problem Date Reported:  1/21/2008 7:30:12 AM
Severity:    Infrequently encountered problem Last Updated: 2/10/2008 5:27:40 AM
Platform:    All versions Internal Tracking #:  
Resolution: Duplicate  Resolved in Build: : 11.0.2627.5503
Duplicate of:  51111
Voting and Rating
Overall Rating: No Ratings Yet
0.00 out of 5
Total Votes: None
Description
Here is another example of inconsistency between ErrorInsight and the actual Delphi compiler.  A declaration like this:

    function Xxxx(Param: Integer): Integer stdcall;
---------------------------------------------------------------^

is seen as an error by ErrorInsight, but is compiled OK. It seems that the "official" syntax does require a semicolon, though.

I've discovered the problem by loading the standard CommCtrl.pas unit and seeing a bunch of ErrorInsight messages it generates.  I haven't checked specifically, but other VCL units are likely to miss some semicolons, too.

Obviously, this is not a serious problem, but ErrorInsight messages on official VCL units look kind of weird, so please consider some cleanup:

-  Add missing semicolons in CommCtrl.pas and whatever other library units that might be using this non-standard syntax;

- Optionally, make ErrorInsight to accept this as valid syntax (although it might be actually better to keep to the documented syntax)


Steps to Reproduce:
Just open CommCtrl.pas and see errors in the ErrorInsight panel.
Workarounds
None
Attachment
None
Comments

Ralf Stocker at 1/21/2008 3:35:38 PM -
http://qc.codegear.com/wc/qcmain.aspx?d=45863

Server Response from: ETNACODE01