Thread overview
[Issue 19612] Wrong(?) code compiles
Jan 24, 2019
Victor Porton
Jan 25, 2019
anonymous4
Dec 17, 2022
Iain Buclaw
Apr 25, 2023
RazvanN
January 24, 2019
https://issues.dlang.org/show_bug.cgi?id=19612

--- Comment #1 from Victor Porton <porton@narod.ru> ---
Hm, it compiles in C with GCC 8.2.0-7ubuntu1 (after removal the module
declaration), too. Weird.

--
January 25, 2019
https://issues.dlang.org/show_bug.cgi?id=19612

anonymous4 <dfj1esp02@sneakemail.com> changed:

           What    |Removed                     |Added
----------------------------------------------------------------------------
           Hardware|x86_64                      |All
                 OS|Linux                       |All

--- Comment #2 from anonymous4 <dfj1esp02@sneakemail.com> ---
C uses this idiom to maintain compatibility between function declarations in the header file and function definitions in the implementation file. When implementation includes the header, the compiler checks that declarations match definitions and can report a warning if they don't. Well, extern just allows to declare a function, and provide implementation elsewhere, not restricted where.

--
December 17, 2022
https://issues.dlang.org/show_bug.cgi?id=19612

Iain Buclaw <ibuclaw@gdcproject.org> changed:

           What    |Removed                     |Added
----------------------------------------------------------------------------
           Priority|P1                          |P3

--
April 25, 2023
https://issues.dlang.org/show_bug.cgi?id=19612

RazvanN <razvan.nitu1305@gmail.com> changed:

           What    |Removed                     |Added
----------------------------------------------------------------------------
             Status|NEW                         |RESOLVED
                 CC|                            |razvan.nitu1305@gmail.com
         Resolution|---                         |INVALID

--