Re: Possible solution for special characters in makefile paths

-----BEGIN PGP SIGNED MESSAGE-----
Hash: SHA1

On 2/20/14, 10:44 AM, Paul Smith wrote:
> On Thu, 2014-02-20 at 09:47 -0800, Bill Cox wrote:
>> Unless someone suggests a truly backward-compatible mechanism, I 
>> recommend that this change trigger at least a major version
>> number change, and possibly (yech) fork the tool.
> 
> Can you provide some justification for that position?  I'm
> interested in recommendations and suggestions, but I'd prefer that
> they come with _some_ supporting arguments.
> 
> Also I don't know what "fork the tool" means.
> 
> There are backward incompatible "edge-case" changes on virtually
> every release of GNU make; see the NEWS file for examples.  Given
> the free-form format of makefiles it's almost impossible to make 
> advancements without encroaching on behaviors somewhere.  It's not 
> immediately clear to me that this change would be more impactful
> than most others, but I'm certainly interested in any real-life
> experiences to the contrary...

Good point.  I wrote before thinking thoroughly.  I hope this is better.

I had one concern; that users not be surprised by make's behavior -
thus the version number change and a forked source base, with the new
major version as one branch and the old lexing behavior in another
branch.   Really bad idea.  I shouldn't post so soon after waking up.

If the new lexing/encoding behavior is turned off by default, and only
explicitly enabled, users are safe from a quiet behavior change, which
removes my concern.

Bill


-----BEGIN PGP SIGNATURE-----
Version: GnuPG/MacGPG2 v2.0.17 (Darwin)
Comment: GPGTools - http://gpgtools.org
Comment: Using GnuPG with Thunderbird - http://www.enigmail.net/

iQEcBAEBAgAGBQJTBtaaAAoJED7Ly9UccgQg0mcH/A0jqbkUVRTo609yrrUzCeWZ
4owcLxiT3P8zeXRerctQgyFpMpdZ+4ebWea+Teaj932ivxro9KLhBjQoAbcaPO+u
MgFIfA/yk5auastq/eIQ/4vwLrqcKcZCwgUfzRocidIDY1un0wa2T1NjtWFU+ecN
5jldNvAnIkBiz8Y/OJFq67GzoE8y6BAXv3Q9JJz9bFXEfNNGVOOM4fsMd9phgMeF
mVzFAGLEeejEZxqNPbiK9nOnaLM84jXwIREkhr5zyS/i/tOLJG6x7Vxbr9jQ2ogr
VaO0V0ggtbpF1EsEHzaZr5Iup8wIwwW9D//pubdvu8SKJ/Y/sjPXQcpP3dhGlSg=
=1Z1N
-----END PGP SIGNATURE-----