C++ Logo


Advanced search

Re: [SG15] module source suffixes

From: Olga Arkhipova <olgaark_at_[hidden]>
Date: Mon, 26 Aug 2019 17:16:53 +0000
VS needs to distinguish module interface files as they require very special treatment in the IDE. Currently, the file extension is used as a hint for file content in many parts of VS. Adding a new extension for components which deal with c++ is not a problem. But not being able to distinguish modules by extension and only by file name suffix will require a lot changes.
So I am strongly for having new extension for module interface files (not just file name suffix).


-----Original Message-----
From: SG15 <sg15-bounces_at_[hidden]> On Behalf Of Matthew Woehlke via SG15
Sent: Monday, August 26, 2019 10:08 AM
To: sg15_at_[hidden]
Cc: Matthew Woehlke <mwoehlke.floss_at_[hidden]>; Nathan Sidwell <nathan_at_[hidden]>
Subject: Re: [SG15] module source suffixes

On 26/08/2019 11.53, Ben Boeckel via SG15 wrote:
> On Mon, Aug 26, 2019 at 10:18:57 -0400, Nathan Sidwell via SG15 wrote:
>> 2) It requires teaching all your tools (and users) that the new
>> suffix means C++.
> FWIW, I don't think CMake is going to care much.

Indeed, build systems and compilers may not care much. However, editors almost certainly will. (At minimum, syntax highlighting data will need to be updated.) So will MIME types databases. It may be worth keeping in mind that not only things like editors will change, but also any library or program (e.g. `file`) that tries to produce a "file type" designation for a file.

That being the case, there may indeed be an argument to be made against introducing a new extension unnecessarily.

SG15 mailing list

Received on 2019-08-26 12:18:57