Subject: Re: [SG15] module source suffixes
From: Michael Spencer (bigcheesegs_at_[hidden])
Date: 2019-08-29 15:08:57
On Thu, Aug 29, 2019 at 11:27 AM Ben Craig via SG15 <sg15_at_[hidden]>
> Editors will also auto-complete poorly, and sometimes "smart indent"
> poorly if the extension isn't recognized. I deal with this on a regular
> basis when I dig into a standard library header.
But in many editors you can fix this by adding a file extension in the
settings, you don't even need to wait for a new version of the editor. (Not
that this works for stdlib headers).
- Michael Spencer
> > -----Original Message-----
> > From: SG15 <sg15-bounces_at_[hidden]> On Behalf Of Matthew
> > Woehlke via SG15
> > Sent: Thursday, August 29, 2019 1:10 PM
> > To: Olga Arkhipova <olgaark_at_[hidden]>; sg15_at_[hidden]; Ville
> > Voutilainen <ville.voutilainen_at_[hidden]>
> > Cc: Matthew Woehlke <mwoehlke.floss_at_[hidden]>
> > Subject: [EXTERNAL] Re: [SG15] module source suffixes
> > On 29/08/2019 13.56, Olga Arkhipova wrote:
> > > Even non compiling editors will need to be aware of new syntax (if not
> > BMIs) to show something meaningful for modules, aren't they?
> > Yeeeees... and no. Lines with module directives may (probably will) mis-
> > highlight, but most of the file should be reasonable.
> > --
> > Matthew
> > _______________________________________________
> > SG15 mailing list
> > SG15_at_[hidden]
> > 15__;!fqWJcnlTkjM!7KnnKrARTAXqQzxAsAAssho9kux63flpxQc0Kt51pw3Ruh
> > GESHhCY8oBadnG$
> SG15 mailing list
SG15 list run by email@example.com