Syntax silliness

[IanH]

It is the season for triviality...

[fortran]MODULE PublicColonsShouldBeBanned
  PUBLIC ::   ! Not permitted by F95 R522 / F2003 R518 / F2008 R524
END MODULE PublicColonsShouldBeBanned[/fortran]

Despite widespread agreement about the sentiment in the module name, the above compiles without error.

[plain]
>ifort /c /warn:all /stand:f95 "2013-01-02 public-colons.f90"
Intel(R) Visual Fortran Compiler XE for applications running on IA-32, Version 13.0.1.119 Build 20121008
Copyright (C) 1985-2012 Intel Corporation.  All rights reserved.

>
[/plain]

[Steven_L_Intel1]

Thanks - I will let the developers know. Issue ID is DPD200239816.

[IanH]

Another (one, (for free form (only))) ... [fortran] SUBROUTINE ThisOneIsOk END SUBROUTINE ButThisOneIsMissingSomething BIND(C) END [/fortran] [plain] >ifort /c /check:all /warn:all /standard-semantics /stand:f03 "2013-01-05 R1234.f90" Intel(R) Visual Fortran Compiler XE for applications running on IA-32, Version 13.0.1.119 Build 20121008 Copyright (C) 1985-2012 Intel Corporation. All rights reserved. > [/plain]

[Steven_L_Intel1]

Thanks - yes, that too is incorrect. (For those wondering, because the BIND(C) suffix is there, () is required after the subroutine name.)

[Steven_L_Intel1]

The PUBLIC:: issue is fixed for a release later this year. The missing error for BIND(C) without the argument list is issue DPD200241568.