Re: cpphs bug with pathnames beginning with more than one slash

On Thu, Jun 09, 2016 at 07:44:55PM -0500, Andrés Sicard-Ramírez wrote: > Hi Dan, > > FYI, cpphs has a (new) bug tracker in > > https://github.com/malcolmwallace/cpphs/issues Would be worth linking to it from the docs and main site. I see t there's an open issue there for that :) -- Dan

Re: cpphs bug with pathnames beginning with more than one slash

Hi Dan, FYI, cpphs has a (new) bug tracker in https://github.com/malcolmwallace/cpphs/issues Best, On 9 June 2016 at 16:11, Dan Aloni wrote: > Hi Malcolm, > > If we pass pathnames starting with more than one slash to '-include', > cpphs generates invalid output. These

cpphs bug with pathnames beginning with more than one slash

Hi Malcolm, If we pass pathnames starting with more than one slash to '-include', cpphs generates invalid output. These are valid UNIX pathnames. I've tested with version 1.20.1 on Linux. Example: $ touch empty.hs $ cpphs --cpp -include //dev/null empty.hs #line 1 "test.hs"