Re: 2.62 AT_SETUP limitations

2008-04-24 Thread Joel E. Denny
On Thu, 24 Apr 2008, Eric Blake wrote: > | I proposed that the result of m4_dquote be passed to m4_bpatsubst. I > | didn't mean that the result of m4_dquote should be passed directly to > | m4_len. > > The point of the example was to demonstrate what happens if you pass > arguments to alternate

Re: 2.62 AT_SETUP limitations

2008-04-24 Thread Eric Blake
-BEGIN PGP SIGNED MESSAGE- Hash: SHA1 According to Joel E. Denny on 4/24/2008 12:31 AM: | This message from Eric was never delivered to me, but I stumbled upon it | in the bug-autoconf archives: | | http://lists.gnu.org/archive/html/bug-autoconf/2008-04/msg00064.html | | Sorry to break

tracing output [was: 2.62 AT_SETUP limitations]

2008-04-24 Thread Eric Blake
-BEGIN PGP SIGNED MESSAGE- Hash: SHA1 According to Akim Demaille on 4/24/2008 3:22 AM: |> -m4_define([m4_expand], [_$0(($1))]) |> +m4_define([m4_expand], [_$0(-=(=-$1-=)=-)]) |> m4_define([_m4_expand], |> -[m4_changequote([(], [)])$1m4_changequote`'m4_changequote(`[', `]')]) |> +[m4_chang

Re: 2.62 AT_SETUP limitations

2008-04-24 Thread Akim Demaille
Le 23 avr. 08 à 02:54, Noah Misch a écrit : --- autoconf/lib/m4sugar/m4sugar.m4.~1.136.~ 2008-04-22 16:19:27.0 -0400 +++ autoconf/lib/m4sugar/m4sugar.m4 2008-04-22 20:50:59.643031187 -0400 @@ -709,9 +709,9 @@ # Exploit that extra () will group unquoted commas and the following # whit

Re: 2.62 AT_SETUP limitations

2008-04-24 Thread Akim Demaille
Le 22 avr. 08 à 14:45, Eric Blake a écrit : Really, the problem is that there is no way to determine whether $1 is safe to expand, short of expanding $1; thus, if it was not safe, you've already screwed up the state of the m4 parsing. I always felt m4 lacks an "eval" macro. Not the one for

Re: 2.62 AT_SETUP limitations

2008-04-23 Thread Joel E. Denny
This message from Eric was never delivered to me, but I stumbled upon it in the bug-autoconf archives: http://lists.gnu.org/archive/html/bug-autoconf/2008-04/msg00064.html Sorry to break threading with this forged reply. On Wed, 23 Apr 2008, Eric Blake wrote: > # example expanders > m4_defin

Re: 2.62 AT_SETUP limitations

2008-04-23 Thread Eric Blake
-BEGIN PGP SIGNED MESSAGE- Hash: SHA1 According to Noah Misch on 4/22/2008 6:54 PM: | | How about this? Keep the parentheses around for space preservation, but make | them part of a more complex quote string. Looks like it should work - in m4_expand, the () appear as balanced parens, bu

Re: 2.62 AT_SETUP limitations

2008-04-23 Thread Eric Blake
-BEGIN PGP SIGNED MESSAGE- Hash: SHA1 According to Joel E. Denny on 4/22/2008 6:14 PM: |> Because AT_SETUP now uses the newly documented m4_expand macro, which in |> turn REQUIRES balanced () because it temporarily uses |> m4_changequote([(],[)]) to force preservation of unquoted space af

Re: 2.62 AT_SETUP limitations

2008-04-22 Thread Joel E. Denny
On Tue, 22 Apr 2008, Eric Blake wrote: > | That's my suggestion as well... except the limitation is that the argument > | must expand properly quoted. In the context of M4, this limitation seems > | more intuitive to me than parentheses balancing. > > But m4_dquote eats space, which ruins line l

Re: 2.62 AT_SETUP limitations

2008-04-22 Thread Noah Misch
On Tue, Apr 22, 2008 at 06:45:26AM -0600, Eric Blake wrote: > According to Joel E. Denny on 4/22/2008 2:36 AM: > | According to Autoconf 2.62's manual, AT_SETUP no longer allows unbalanced > | parentheses to appear in test case titles. This regression breaks CVS > | Bison's test suite, which worke

Re: 2.62 AT_SETUP limitations

2008-04-22 Thread Eric Blake
-BEGIN PGP SIGNED MESSAGE- Hash: SHA1 According to Joel E. Denny on 4/22/2008 2:36 AM: Hello Joel, | According to Autoconf 2.62's manual, AT_SETUP no longer allows unbalanced | parentheses to appear in test case titles. This regression breaks CVS | Bison's test suite, which worked fine

Re: 2.62 AT_SETUP limitations

2008-04-22 Thread Joel E. Denny
On Tue, 22 Apr 2008, Eric Blake wrote: > | Instead of adding the precondition "no unbalanced parentheses" to > | AT_SETUP, why not add the precondition "the argument must expand properly > | quoted"? > > Because AT_SETUP now uses the newly documented m4_expand macro, which in > turn REQUIRES bala

Re: 2.62 AT_SETUP limitations

2008-04-22 Thread Ralf Wildenhues
Hello, * Eric Blake wrote on Tue, Apr 22, 2008 at 02:45:26PM CEST: > Sounds like we need to add a new quadrigraph for ( and ), then. Any > suggestions for the two middle characters? What about @<.@ @.>@ ? They have the slight disadvantage that the dot usually needs a backslash within a regular

2.62 AT_SETUP limitations

2008-04-22 Thread Joel E. Denny
Hi, According to Autoconf 2.62's manual, AT_SETUP no longer allows unbalanced parentheses to appear in test case titles. This regression breaks CVS Bison's test suite, which worked fine with 2.61, and it seems like an unnecessary limitation. Bison's test suite contains a series of test cases