Date: Thu, 29 Aug 2019 20:21:43 +0300
On Thu, 29 Aug 2019 at 20:03, Olga Arkhipova via SG15
<sg15_at_[hidden]> wrote:
>
> I’d like to better understand the reasons why people find new file extension for module interface sources problematic/undesirable. Can somebody describe some scenarios where new extension will cause problems while having modules with old extension will not?
A bit less than 20 years ago, half of my tools didn't think .cpp is a
c++ source file, and the other half
didn't think .C or .cc are. That was not a pleasant experience. While
such problems are temporary by nature,
they are annoying.
<sg15_at_[hidden]> wrote:
>
> I’d like to better understand the reasons why people find new file extension for module interface sources problematic/undesirable. Can somebody describe some scenarios where new extension will cause problems while having modules with old extension will not?
A bit less than 20 years ago, half of my tools didn't think .cpp is a
c++ source file, and the other half
didn't think .C or .cc are. That was not a pleasant experience. While
such problems are temporary by nature,
they are annoying.
Received on 2019-08-29 12:23:59