Re: [groff] Loss of MSVC support

2019-02-14 Thread Colin Watson
On Wed, Feb 13, 2019 at 06:58:18PM +0200, Eli Zaretskii wrote: > Just to make what Keith says (and I concur) crystal clear: there's a > need to distinguish between C99 compliance of the compiler and the > C99/Posix compliance of the C runtime. We can assume the former, > certainly when using MinGW

Re: [groff] Loss of MSVC support

2019-02-14 Thread John Gardner
> but there's also no great urgency to remove them, IMO Agreed. Personally, I think this is a non-issue. If Groff still uses backticks to support the (pre-POSIX) ancient Bourne Shell for Solaris 9-10, then we may as well remove those too if we're "modernising" the codebase... (I use "modernise"

Re: [groff] Loss of MSVC support

2019-02-14 Thread Walter Harms
> John Gardner hat am 14. Februar 2019 um 14:20 > geschrieben: > > > > but there's also no great urgency to remove them, IMO > > Agreed. Personally, I think this is a non-issue. > > If Groff still uses backticks to support the (pre-POSIX) ancient Bourne > Shell for Solaris 9-10, then we may

Re: [groff] Loss of MSVC support

2019-02-14 Thread Eli Zaretskii
> From: Doug McIlroy > Date: Wed, 13 Feb 2019 16:00:13 -0500 > > I run groff on windows a lot, but via cygwin, which emulates > Unix. I am inclined to think that if you like the groff toolset, > you are likely to want other Unix capability, too, and thus > gravitate towards facilities like cygwin

Re: [groff] Loss of MSVC support

2019-02-14 Thread Eli Zaretskii
> From: John Gardner > Date: Thu, 14 Feb 2019 09:18:15 +1100 > Cc: groff > > I admit I don't have much to contribute to this discussion, but I haven't > seen GOW mentioned yet, so I figure I'd bring it up for those who'd be > interested: > > https://github.com/bmatzelle/gow That was last updat

Re: [groff] Loss of MSVC support

2019-02-14 Thread Eli Zaretskii
> Date: Thu, 14 Feb 2019 12:50:09 + > From: Colin Watson > > On Wed, Feb 13, 2019 at 06:58:18PM +0200, Eli Zaretskii wrote: > > Just to make what Keith says (and I concur) crystal clear: there's a > > need to distinguish between C99 compliance of the compiler and the > > C99/Posix compliance

Re: [groff] Loss of MSVC support

2019-02-14 Thread John Gardner
> That was last updated 5 years ago, and most of the activity ended 7 years ago I know. The author's recent activity suggests lack of time and/or interest, but according to a recent post , the project is still maintained.

Re: [groff] Loss of MSVC support

2019-02-14 Thread Colin Watson
On Thu, Feb 14, 2019 at 07:30:13PM +0200, Eli Zaretskii wrote: > > Date: Thu, 14 Feb 2019 12:50:09 + > > From: Colin Watson > > > > If it's just the runtime, then Gnulib should be able to paper over a > > pretty fair number of the differences, and groff already uses that. > > Up to a degree.

Re: [groff] Loss of MSVC support

2019-02-14 Thread John Gardner
> who has access to both Windows and non-Windows tes platforms and > wants to try to reduce the Windows support burden in groff. Microsoft have a CI service called AppVeyor that offers pretty decent build configuration. For a free service, it's actually not bad. There's