Re: RFC: new changeresyntax builtin

, `EMACS')') define(`m4_patsubst', `m4_builtin(`patsubst', `$1', `$2', `$3', `POSIX_EXTENDED')') define(`m4_ipatsubst', `m4_builtin(`patsubst', `$1', `$2', `$3', `POSIX_EXTENDED,insensitive')') It still makes sense to pro

GNU M4 1.4.5 released

the number of sub-expressions in the regexp. Version 1.4.4b - 17 June 2006, by Eric Blake (CVS version 1.4.4a) * Fix a recursive push_string crashing bug, which affected changequote of three or more characters on some compilers. * Use automake to fix build portability issues. * Fix a recur

m4-1.4.6 soon?

nt in all earlier versions, but my testsuite improvements in 1.4.5 made it much more visible), and bugs in stream handling. Would posting a snapshot tarball be helpful to anyone? - -- Life is short - so eat dessert first! Eric Blake [EMAIL PROTECTED] -BEGIN PGP SIGNATURE- Ve

rfc: new __program__ macro

ut the .exe that internal error messages used. - -- Life is short - so eat dessert first! Eric Blake [EMAIL PROTECTED] -BEGIN PGP SIGNATURE- Version: GnuPG v1.4.2.1 (Cygwin) Comment: Public key at home.comcast.net/~ericblake/eblake.gpg Co

Re: rfc: new __program__ macro

-BEGIN PGP SIGNED MESSAGE- Hash: SHA1 Hi Gary, According to Gary V. Vaughan on 8/4/2006 2:50 AM: > Hi Eric, > > Eric Blake wrote: >> Would it be worth adding __program__ macro, to go along with __file__ and >> __line__, which expands to argv[0] in the same manne

Re: rfc: new __program__ macro

Eric Blake byu.net> writes: Hi Gary, > > > Man, I wish I could get glibc to provide a va_list variant of > > error/error_at_line (I'm in the process of proposing that, trying to bring > > gnulib and glibc back in sync and fix other bugs in the error.c module). &

Re: m4-1.4.6 soon?

test > ../../checks/103.platform_m: stdout mismatch > 5c5 > < 1 > --- > > 0 OK, so AIX 4 didn't provide any of the usual preprocessor macros such as __unix__. What DOES it provide, that we can key off of in src/m4.h to determine whether we should treat i

Re: [bug-gnulib] VPATH and IRIX make (was: m4-1.4.6 soon?)

and document it properly in the autoconf manual, I think it would be wiser for gnulib to support this particular usage. That said, I will not hold up the m4 1.4.6 release waiting for a workaround. -- Eric Blake ___ M4-discuss mailing list M4-disc

dumpdef output stream

ssert first! Eric Blake [EMAIL PROTECTED] -BEGIN PGP SIGNATURE- Version: GnuPG v1.4.2.1 (Cygwin) Comment: Public key at home.comcast.net/~ericblake/eblake.gpg Comment: Using GnuPG with Mozilla - http://enigmail.mozde

RFC: m4 2.0 --prepend-include option

searches would be disabled in the GNU version thanks to the implicit -G. This patch also fixes 'm4 --help --version' to display help, consistent with coreutils, rather than its current behavior of showing the version. 2006-08-23 Eric Blake <[EMAIL PROTECTED]> * src/main

Re: RFC: m4 2.0 --prepend-include option

-BEGIN PGP SIGNED MESSAGE- Hash: SHA1 [dropping autoconf] According to Paul Eggert on 8/23/2006 11:59 AM: > Eric Blake <[EMAIL PROTECTED]> writes: > >> So by that proposal, a user could then do 'POSIXLY_CORRECT=1 m4 >> -B1024' to get the same behavior

Re: RFC: m4 2.0 --prepend-include option

#x27;m pretty sure the answer will be "yes" given > the longstanding default behavior of GNU M4). Hmm, that's not quite what we thought earlier: http://lists.gnu.org/archive/html/m4-patches/2003-06/msg00035.html I'll go ahead and file that aardvark. - -- Life is short - s

Re: RFC: m4 2.0 --prepend-include option

oup decides to add text in the normative section as well. But hopefully the final resolution will be that GNU's behavior (popdef/pushdef) is compliant, as I agree it is better. - -- Life is short - so eat dessert first! Eric Blake [EMAIL PROTECTED] -BEGIN PGP SIGNATURE- Versi

multidigit arguments [was: RFC: m4 2.0 --prepend-include option]

(if you want to pursue it) since I know better where the bodies are > buried. > There are still a couple of other undiscussed ERNs that will impact m4 and POSIXLY_CORRECT behavior, and I am still debating about submitting an aardvark regarding whether blind macros are permissible. - -- Life i

GNU M4 1.4.6 released

#x27; and any other information that might be useful in resolving the issue. - -- Eric Blake -BEGIN PGP SIGNATURE- Version: GnuPG v1.4.2.1 (Cygwin) Comment: Public key at home.comcast.net/~ericblake/eblake.gpg Comment: Using GnuPG with Mozilla - http://enigmail.mozdev.org iD8DBQFE7wrx84KuGfS

Re: RFC: m4 2.0 --prepend-include option

-BEGIN PGP SIGNED MESSAGE- Hash: SHA1 According to Eric Blake on 8/23/2006 9:24 AM: > Here is my proposal for adding a --prepend-include option to m4 2.0, so > that once autom4te requires 2.0, it can search for files outside of the > current working directory first. I've

RFC: rename symbols to m4symbols

eds to pick up from CVS M4, such as changeresyntax. Also, is it worth putting the macros in the load module in a proper namespace? "modules", "load", and "unload" are all English words, but at least with CVS m4, you have to explicitly request "-m load" a

Re: RFC: rename symbols to m4symbols

Hi Gary, > Hi Eric! > > On 18 Sep 2006, at 14:09, Eric Blake wrote: >>> "symbols" is an English word, but was added to m4-1.4o as a macro that >>> takes 0 arguments (even worse, the 1.4o manual documented the new macro, >>> but NEWS did not). Th

GNU M4 1.4.7 released

u will then need to have the latest release versions of Automake (1.9.6) and Autoconf (2.60) installed to bootstrap the checked out sources yourself. Please report bugs to , along with the output of 'make check' and any other information that might be useful in resolving the issue. - -- Eric

RFC: enhancement to builtin

w this could be useful. Any objections to installing this? 2006-10-15 Eric Blake <[EMAIL PROTECTED]> * m4/macro.c (expand_argument): Fix missing initialization. * m4/m4private.h (struct m4_symbol_value): Store entire m4_builtin, not just the func. (m4_

whitespace vs. POSIX

vtools/m4/m4.h?revision=1.1&view=markup - -- Life is short - so eat dessert first! Eric Blake [EMAIL PROTECTED] -BEGIN PGP SIGNATURE- Version: GnuPG v1.4.2.1 (Cygwin) Comment: Public key at home.comcast.net/~ericblake/eblake.gpg Comment: Using GnuPG with Mozilla - http://e

Re: RFC: enhancement to builtin

Eric Blake byu.net> writes: > > > Here's a proposal for enhancing the 'builtin' macro to make it possible to > recover a builtin macro, even if all references to it have been undefined. > Hopefully, the proposed documentation in the patch will give some mo

ideas on changesyntax

way to disable comments. Any comments before I proceed on this path? - -- Life is short - so eat dessert first! Eric Blake [EMAIL PROTECTED] -BEGIN PGP SIGNATURE- Version: GnuPG v1.4.2.1 (Cygwin) Comment: Public key at home.comcast.net/~ericblake/eblake.gpg Comment: U

Re: RFC: enhancement to builtin

-BEGIN PGP SIGNED MESSAGE- Hash: SHA1 According to Eric Blake on 10/27/2006 11:02 AM: >> Here's a proposal for enhancing the 'builtin' macro to make it possible to >> recover a builtin macro, even if all references to it have been undefined. >> Hopeful

Re: GNU M4 1.4.8 released

-BEGIN PGP SIGNED MESSAGE- Hash: SHA1 According to Santiago Vila on 11/27/2006 4:48 PM: > On Mon, 20 Nov 2006, Eric Blake wrote: > >> The changes in this version trigger spurious testsuite failures in the >> Autoconf 2.60 testsuite; if you use GNU Autoconf, it is sug

POSIX vs. eval

hard, make some time for fun as well! Eric Blake [EMAIL PROTECTED] -BEGIN PGP SIGNATURE- Version: GnuPG v1.4.5 (Cygwin) Comment: Public key at home.comcast.net/~ericblake/eblake.gpg Comment: Using GnuPG with Mozilla - http://enigmail.mozdev.org iD8DBQFFk9en84KuGfSFAYARAm2

Re: POSIX vs. eval

-BEGIN PGP SIGNED MESSAGE- Hash: SHA1 According to Gary V. Vaughan on 12/29/2006 1:27 PM: > Hi Eric, Hi Gary, and happy new year, > > On 28 Dec 2006, at 14:41, Eric Blake wrote: >> The current wording of the m4 eval macro forbids implementations from >>

Re: 2.0 snapshots

and the worse thing is that we (PLD) > are using these. We would like to use/test never ones so it would be nice to > see some recent snap release. > OK, I'll try to put something up in the near future. - -- Don't work too hard, make some time for fun as well! Eric

Re: M4 syntax $11 vs. ${11}

-BEGIN PGP SIGNED MESSAGE- Hash: SHA1 According to Ralf Wildenhues on 1/18/2007 10:35 AM: [ Can we limit this to, say, the m4-discuss and autoconf lists? ] Sure. > > Hi Eric, Hi Ralf, and thanks for the feedback, > > * Eric Blake wrote on Thu, Jan 18, 2007 at 03

Re: M4 syntax $11 vs. ${11}

-BEGIN PGP SIGNED MESSAGE- Hash: SHA1 According to Eric Blake on 1/18/2007 7:50 AM: > > With 1.9b, I would like to implement the resolution of XCU ERN 111. That > is, I plan on adding support for ${11}, so that the GNU extension of more > than 9 parameters is still alive (an

Re: newbie question: conditional inclusion

u.org/software/m4/manual/html_node/Conditionals.html#Conditionals, (also available as 'info m4 conditionals' if you installed the documentation properly), and let us know if there is anything we can do to improve the manual. - -- Don't work too hard, make some time for fun as well!

Re: M4 syntax $11 vs. ${11}

-BEGIN PGP SIGNED MESSAGE- Hash: SHA1 According to Paul Eggert on 1/20/2007 12:43 AM: > Eric Blake <[EMAIL PROTECTED]> writes: > >> + /* This warning must not kill m4 -E, or it will break autoconf. */ >> + if (text && strstr (text, "${")) >

Re: M4 syntax $11 vs. ${11}

-BEGIN PGP SIGNED MESSAGE- Hash: SHA1 According to Eric Blake on 1/19/2007 7:24 AM: > According to Ralf Wildenhues on 1/18/2007 10:35 AM: > [ Can we limit this to, say, the m4-discuss and autoconf lists? ] Actually, this particular mail can probably stay on just autoconf-p

Re: M4 syntax $11 vs. ${11}

-BEGIN PGP SIGNED MESSAGE- Hash: SHA1 According to Paul Eggert on 1/28/2007 2:40 AM: > Eric Blake <[EMAIL PROTECTED]> writes: > >> Here's an updated (and smaller) patch that makes CVS autoconf happy with >> branch-1_4 of M4, after today's commit that

Re: M4 syntax $11 vs. ${11}

-BEGIN PGP SIGNED MESSAGE- Hash: SHA1 According to Paul Eggert on 1/29/2007 10:39 AM: > Eric Blake <[EMAIL PROTECTED]> writes: > >> Because I was hoping that M4 2.0 could borrow a leaf from shell parsing, >> and ALSO implement things like ${1-default} that

Re: M4 syntax $11 vs. ${11}

d. It took me a while to find all the false positives in autoconf, automake, and libtool, particularly when my first cut at the patch was even more vocal about plain '${', with the one-by-one approach. - -- Don't work too hard, make some time for fun as well! Eric Blake [

Re: AIX 4.3.3 IBM C compiler patch for m4-1.4.8

en we should figure out how to make the gnulib bool pick a type that will work for this usage pattern. - -- Don't work too hard, make some time for fun as well! Eric Blake [EMAIL PROTECTED] -BEGIN PGP SIGNATURE- Version: GnuPG v1.4.5 (Cygwin) Comment: Public

Re: AIX 4.3.3 IBM C compiler patch for m4-1.4.8

dea isn't worth it, then I guess I will have to change m4 to avoid bool bitfields. - -- Don't work too hard, make some time for fun as well! Eric Blake [EMAIL PROTECTED] -BEGIN PGP SIGNATURE- Version: GnuPG v1.4.5 (Cygwin) Comment: Public key at home.comcast.net/~eric

Re: 'make check' from system() under Python

the Fedora m4 pages? I would be interested in tracking if they have any other useful things that should be added upstream. > I tried removing SIGPIPE from lib/fatal-signal.c but that didn't help. lib/fatal-signal.c is maintained in gnulib; it would be worth asking there for more on w

Re: 'make check' from system() under Python

-BEGIN PGP SIGNED MESSAGE- Hash: SHA1 According to Eric Blake on 2/4/2007 9:26 PM: > Probably something to do with inherited signal handling and python's > choice of what signals to ignore. I don't know whether the bug is in > python for ignoring a signal that the ch

Re: 'make check' from system() under Python

-BEGIN PGP SIGNED MESSAGE- Hash: SHA1 According to Eric Blake on 2/4/2007 9:45 PM: > > I'm thinking that I'll just change the test to use SIGKILL only, since we > have proven that SIGPIPE is risky to rely on portably. M4 doesn't have a > bug, so much as the te

Re: AIX 4.3.3 IBM C compiler patch for m4-1.4.8

d' instead to make it more clear what was going on. But thanks for the report - it is now fixed in CVS. - -- Don't work too hard, make some time for fun as well! Eric Blake [EMAIL PROTECTED] -BEGIN PGP SIGNATURE- Version: GnuPG v1.4.5 (Cygwin) Commen

Re: M4 syntax $11 vs. ${11}

-BEGIN PGP SIGNED MESSAGE- Hash: SHA1 According to Eric Blake on 1/30/2007 7:23 AM: > > Let me think on this for a couple more days (as it is, I still haven't > completely implemented extended arguments in CVS m4; partly because I want > to do it right, so I want this th

Re: M4 syntax $11 vs. ${11}

t; EOF m4:stdin:1: Warning: definition of `foo' contains sequence `$001' $ I thought it more user-friendly to pick up the entire string of digits, rather than stopping at the second. - -- Don't work too hard, make some time for fun as well! Eric Blake [EMAIL PROT

Re: Comments on changesyntax et al.

ers, so maybe I should just reserve ALL ${ sequences in the default warning of M4 1.4.9's --warn-macro-sequence. Like I said, it will be a couple of weeks before I have any more M4 hacking time, but I appreciate your feedback on the work in progress. -- Eric Blake ___ M4-discuss mailing list M4-discuss@gnu.org http://lists.gnu.org/mailman/listinfo/m4-discuss

Re: building HEAD needs GNU make

-BEGIN PGP SIGNED MESSAGE- Hash: SHA1 [adding m4-discuss - this was http://thread.gmane.org/gmane.comp.gnu.libtool.patches/7289] According to Ralf Wildenhues on 2/24/2007 7:13 AM: >> * Eric Blake wrote on Sat, Feb 24, 2007 at 02:03:43PM CET: >>> According to Ralf Wildenhu

Re: Comments on changesyntax et al.

-BEGIN PGP SIGNED MESSAGE- Hash: SHA1 According to Eric Blake on 2/10/2007 4:22 PM: > > Paul convinced me that for purposes > of a transition period, only ${ should be recognized as > the start of an extended argument. On the other hand, that was > before we came up wi

GNU M4 1.4.8b released (beta release)

Autoconf 2.62 will be compatible with this option. * Improved portability to platforms such as BSD/OS and AIX. Please report bugs to , along with the output of 'make check' and any other information that might be useful in resolving the issue. - -- Eric Blake -BEGIN PGP SIGNATURE--

Re: GNU M4 1.4.8b released (beta release)

-O fixes it (by detecting the brokenness of your compiler's long long), then it probably is not worth much further effort in gnulib to work around it. - -- Don't work too hard, make some time for fun as well! Eric Blake [EMAIL PROTECTED] -BEGIN PGP SIGNATURE- V

Re: GNU M4 1.4.8b released (beta release)

.h in your case that we could do that? Do things work for you if you manually append those three lines to the end of your config.h? - -- Don't work too hard, make some time for fun as well! Eric Blake [EMAIL PROTECTED] -BEGIN PGP SIGNATURE- Version: GnuPG v1.4.5 (Cygwi

Re: GNU M4 1.4.8b released (beta release)

e sys/stat.h prior to redefining all the 64-bit type names, along with any other system header that uses int64_t on your platform. - -- Don't work too hard, make some time for fun as well! Eric Blake [EMAIL PROTECTED] -BEGIN PGP SIGNATURE- Version: GnuPG v1.4.5 (Cygwin) C

Re: M4 syntax $11 vs. ${11}

that we could go so far as to build a module 'm4-14x' vs the existing 'gnu' module, so that from the command-line, 'm4 --gnu' loads all 2.0 features, 'm4 --14x' loads only features in 1.4.x, and 'm4' loads whichever of the two modules was selected to be

Re: GNU M4 1.4.8b released (beta release)

if that's an issue > or not, since so far we aren't talking about any networking apps). > Shouldn't matter - gnulib can't redefine 'long long' since it occupies multiple tokens; and as long as gnulib doesn't use long long, we shouldn't be running afoul

Re: GNU M4 1.4.8b released (beta release)

-BEGIN PGP SIGNED MESSAGE- Hash: SHA1 According to Eric Blake on 3/5/2007 7:15 AM: > According to Matthew Woehlke on 3/2/2007 9:33 AM: >>> Another option would be to leave int64_t defined as it is, but set >>> HAVE_INT64_T >>> to 0, to indicate that gnulib sh

Re: GNU M4 1.4.8b released (beta release)

ual M4 2.0. - -- Don't work too hard, make some time for fun as well! Eric Blake [EMAIL PROTECTED] -BEGIN PGP SIGNATURE- Version: GnuPG v1.4.5 (Cygwin) Comment: Public key at home.comcast.net/~ericblake/eblake.gpg Comment: Using GnuPG with Mozilla - http://enigmail.mozdev.

Re: GNU M4 1.4.8b released (beta release)

he same width, or claim that neither is usable; but as yours is the only odd platform encountered so far, and since CFLAGS=-O appears to solve it for you, I'm not sure how others feel about trying to improve gnulib in this area. It may end up that I release m4 1.4.9 and you have to compile with o

Re: GNU M4 1.4.8b released (beta release)

-BEGIN PGP SIGNED MESSAGE- Hash: SHA1 According to Bruno Haible on 3/10/2007 8:25 AM: > Eric Blake wrote: >> 2007-03-10 Eric Blake <[EMAIL PROTECTED]> >> and Matthew Woehlke(tiny change) >> >> * lib/stdint_.h (int64_t, uint64_t): Don'

Re: GNU M4 1.4.8b released (beta release)

NT) > # undef HAVE_LONG_LONG_INT > #endif Is it worth patching autoconf's AC_TYPE_LONG_LONG_INT macro to declare that there is not a usable 'long long int' type if no corresponding unsigned long long type exists? - -- Don't work too hard, make some time for fun as well! Eric Blak

Re: GNU M4 1.4.8b released (beta release)

-BEGIN PGP SIGNED MESSAGE- Hash: SHA1 According to Eric Blake on 3/10/2007 4:12 PM: > Is it worth patching autoconf's AC_TYPE_LONG_LONG_INT macro to declare > that there is not a usable 'long long int' type if no corresponding > unsigned long long type exists? N

GNU M4 1.4.9 released

ves portability to a number of platforms, and tightens its conformance to various POSIX rules. Version 1.4.9 - 23 Mar 2007, by Eric Blake (CVS version 1.4.8c) * Minor documentation and portability cleanups. Version 1.4.8b - 24 Feb 2007, by Eric Blake (CVS version 1.4.8a) * Fix a regression intr

Re: empty TIMESTAMP, stamp-vcl

te' or 'gnulib-tool --import' would touch a timestamp file that could then be incorporated into the project. - -- Don't work too hard, make some time for fun as well! Eric Blake [EMAIL PROTECTED] -BEGIN PGP SIGNATURE- Version: GnuPG v1.4.5 (Cygwin) Comment: Pub

Re: Size of m4 executable

ween the two compiles. - -- Don't work too hard, make some time for fun as well! Eric Blake [EMAIL PROTECTED] -BEGIN PGP SIGNATURE- Version: GnuPG v1.4.5 (Cygwin) Comment: Public key at home.comcast.net/~ericblake/eblake.gpg Comment: Using GnuPG with Mozilla -

Re: PCRE regex syntax

on.) It would be similar to how the third-party gmp library is handled for the mpeval module. - -- Don't work too hard, make some time for fun as well! Eric Blake [EMAIL PROTECTED] -BEGIN PGP SIGNATURE- Version: GnuPG v1.4.5 (Cygwin) Comment: Public key at home.comca

Re: Macro + diversion issue

en they say that the policy of a consistent interface of one level of quoting per level of parentheses is the easiest way to have predictable results. - -- Don't work too hard, make some time for fun as well! Eric Blake [EMAIL PROTECTED] -BEGIN PGP SIGNATURE-

Re: Macro + diversion issue

a couple of days, I will probably commit a variant of your patch to HEAD only which allows an optional second argument to divert that will be output immediately to the new diversion, but where the divert macro always changes the current diversion, as it has always done. - -- Don't

Re: CVS build breakage

re errors] > > modules/m4.c is not pulling in gnu/stdint.h in its header tree. Adding > "#include " to $builddir/m4/system.h fixed the problem for > me. Thanks for the report. Obviously cygwin's headers are a bit leaky in their namespace, to get intmax_t from somewhere

GNU M4 1.4.9b released (beta release)

check' and any other information that might be useful in resolving the issue. - -- Eric Blake The GNU M4 team -BEGIN PGP SIGNATURE- Version: GnuPG v1.4.5 (Cygwin) Comment: Public key at home.comcast.net/~ericblake/eblake.gpg Comment: Using GnuPG with Mozilla - http://enigmail.mozdev.org iD8DBQF

Re: format bug

-BEGIN PGP SIGNED MESSAGE- Hash: SHA1 According to Eric Blake on 5/28/2007 10:15 PM: > Try this for a fun time: > > $ echo 'format(%*.*d,-1,-1,1)' | m4 | wc > 1 1 2280281 > A related question I have about the format builtin: Consider printf(1).

Re: format bug

ing other warnings? - -- Don't work too hard, make some time for fun as well! Eric Blake [EMAIL PROTECTED] -BEGIN PGP SIGNATURE- Version: GnuPG v1.4.5 (Cygwin) Comment: Public key at home.comcast.net/~ericblake/eblake.gpg C

Re: Macro + diversion issue

s ago in handling hand-crafted frozen files. Here's what I'm checking in to head. I'm porting the regression fix, but not the new feature, to the branch. 2007-05-31 Eric Blake <[EMAIL PROTECTED]> Add extension to divert builtin. * modules/m4.c (builtin_divert): I

Re: format bug

rgument - if you are computing a value, it is just as easy to compute it in octal or hex to begin with. For example, format(`%b', `\0'eval(computation, `8')) - -- Don't work too hard, make some time for fun as well! Eric Blake [EMAIL PROTECTED] -

Re: format bug

-BEGIN PGP SIGNED MESSAGE- Hash: SHA1 According to Daniel Richard G. on 5/31/2007 7:06 PM: > On Thu, 2007 May 31 13:23:28 -0600, Eric Blake wrote: >>> Leery of making "%c" == "%.1s". This behavior doesn't seem terribly useful. >> But it wo

GNU M4 1.4.10 released

' and any other information that might be useful in resolving the issue. - -- Eric Blake The GNU M4 team -BEGIN PGP SIGNATURE- Version: GnuPG v1.4.5 (Cygwin) Comment: Public key at home.comcast.net/~ericblake/eblake.gpg Comment: Using GnuPG with Mozilla - http://enigmail.

license question

refer to LGPL 2.1 in CVS. I'm thinking the best thing to do is just remove COPYING.LIB, but I wanted to make sure before doing it. - -- Don't work too hard, make some time for fun as well! Eric Blake [EMAIL PROTECTED] -BEGIN PGP SIGNATURE- Version: GnuPG v1.4.5 (

Re: license question

-BEGIN PGP SIGNED MESSAGE- Hash: SHA1 According to Gary V. Vaughan on 8/4/2007 1:38 PM: > Hi Eric, Hi Gary, > > Sorry for the late reply. That's fine. > > On Jul 25, 2007, at 12:04 AM, Eric Blake wrote: >> While cleaning up the GPLv3 update, I noticed t

tracing through indir

27;) be traced? Also, this special-casing of traceon cannot be done via the command-line option '--trace/-t'; I wonder if we would need to add something like '--trace-builtin' (no short option). - -- Don't work too hard, make some time for fun as well! Eric Blake

Re: Multi-Line Definitions

x27;ve given me a good idea - I'll try instrumenting a version of m4 and coming up with a good list of the most popular regex patterns in use by autoconf (autoconf -t has limitations, since regex patterns tend to mess up the quoting of the trace file). - -- Don't work too hard, make so

Re: Multi-Line Definitions

-BEGIN PGP SIGNED MESSAGE- Hash: SHA1 According to Eric Blake on 9/29/2007 1:04 PM: > You've given me a good idea - I'll try instrumenting a version of m4 and > coming up with a good list of the most popular regex patterns in use by > autoconf (autoconf -t has limit

m4sugar speedups [was: Multi-Line Definitions]

-BEGIN PGP SIGNED MESSAGE- Hash: SHA1 [this portion of the thread can live on just autoconf-patches] According to Eric Blake on 9/29/2007 1:31 PM: > Also, some of those most frequent patterns can be done with index() rather > than regexp() in m4sugar, offering some speedups even w

m4 regex usage [was: Multi-Line Definitions]

-BEGIN PGP SIGNED MESSAGE- Hash: SHA1 [adding m4-patches; this branch of the thread can drop other lists] According to Eric Blake on 9/29/2007 1:31 PM: > Here's something a bit more telling. With the attached patch, and in the > coreutils directory, > > $ M4_TRACE_F

Re: m4sugar speedups [was: Multi-Line Definitions]

se overquoted $1. Now, if m4 could provide a regex builtin that spit out quoted output, we could fix m4_bpatsubsts to not overquote (hence the m4 TODO to add the qindir builtin). - -- Don't work too hard, make some time for fun as well! Eric Blake [EMAIL PROTECTED] -BEGIN PGP

Re: gnulib request

too hard, make some time for fun as well! Eric Blake [EMAIL PROTECTED] -BEGIN PGP SIGNATURE- Version: GnuPG v1.4.5 (Cygwin) Comment: Public key at home.comcast.net/~ericblake/eblake.gpg Comment: Using GnuPG with Mozilla - h

Re: Multi-Line Definitions

-BEGIN PGP SIGNED MESSAGE- Hash: SHA1 According to Eric Blake on 9/29/2007 1:31 PM: > Here's something a bit more telling. With the attached patch, and in the > coreutils directory, > > $ M4_TRACE_FILE=~/m4.trace M4=~/m4/src/m4 autoconf > $ wc m4.trace > 62207

Re: Fix m4_join

-BEGIN PGP SIGNED MESSAGE- Hash: SHA1 Ideas from an interesting thread on the autoconf-patches list: According to Eric Blake on 10/15/2007 1:45 PM: > Ralf Wildenhues gmx.de> writes: > >> Now it would be even better if m4_join were >> efficient in that it would no

Re: buildbot for m4 latest git version

an something like 2.61a.265-0cb7? > > A quick links page: > > http://www.proulx.com/sys/build-daemons/ > > Bob Thanks for doing this. - -- Don't work too hard, make some time for fun as well! Eric Blake [EMAIL PROTECTED] -BEGIN PGP SIGNATURE

Re: Document [Austin-117:XCU:m4 maketemp, mkstemp Proposed] created

-BEGIN PGP SIGNED MESSAGE- Hash: SHA1 According to Eric Blake on 10/7/2006 4:33 PM: > In line with the two aardvarks I just filed against mkstemp(3), I propose > this wording for the mkstemp paragraph in interpretation 117 (the rest of > the proposed solution is fine as is): &g

Re: How to dinamically set VERSION for AC_INIT

-BEGIN PGP SIGNED MESSAGE- Hash: SHA1 [adding m4-discuss for a discussion on syscmd/esyscmd behavior] According to Eric Blake on 12/14/2007 8:05 AM: > According to Andreas Schwab on 12/14/2007 7:56 AM: >> AC_INIT(my-fine-package, m4_esyscmd([./version.sh | tr -d '\n'

listing currently defined macros

the sorting, but since we don't have any other builtin that sorts or even does lexicographic comparisons, it is rather interesting to consider. - -- Don't work too hard, make some time for fun as well! Eric Blake [EMAIL PROTECTED] -BEGIN PGP SIGNATURE- Version: Gn

Re: m4 module loader interface simplifications

bly named text file or predictably named dso? At which point, you name `dir' according to the module it is providing? Seems reasonable. It would be interesting to see code along these lines, to help decide how maintainable this approach would be. - -- Don't work too hard, make so

Re: listing currently defined macros

g regex builtins (either we would do glob->regex translation ourselves, or we would have to decide between re_search vs. fnmatch). - -- Don't work too hard, make some time for fun as well! Eric Blake [EMAIL PROTECTED] -BEGIN PGP SIGNATURE- Version: GnuPG v1.4.5 (Cygwin)

M4 1.4.10b [beta] released

gpg --keyserver wwwkeys.pgp.net --recv-keys F4850180 and rerun the `gpg --verify' command. This release was bootstrapped with the following tools: ~ Autoconf 2.61a.360-45ab ~ Automake 1.10a ~ Gnulib v0.0-295-g511e2bf NEWS * Noteworthy changes in Version 1.4.10b (2008-02-25) [beta] ~ Released by

Re: M4 1.4.10b [beta] released

uno's mail. Also, if I bump the branch to 1.5, I'd like to turn on i18n on the branch. ~ Which means there will have to be at least one more beta release in order to give the translation teams time to work. - -- Don't work too hard, make some time for fun as well! Eric Blake

Re: M4 1.4.10b [beta] released

ddress of the first character of either C1 or C2, treated as unsigned int, that occurs within the first N bytes of S; else return NULL if neither character occurs. */ void *memchr2 (void const *s, int c1, int c2, size_t n); - -- Don't work too hard, make some time for fun as well! Eric Bla

Re: next_char inlining

NULL if neither character occurs. */ |> void *memchr2 (void const *s, int c1, int c2, size_t n); | | Yes, I see where this function would come in handy. OK, I'll tackle the gnulib module for this soon (I'm also in the middle of working on improving the gnulib strtod module

Re: next_char inlining

Eric Blake byu.net> writes: > | > |> ~ I'm also considering adding a placeholder input block that always results > |> in CHAR_EOF, so that isp is guaranteed to be non-null and we have one less > |> branch in this loop. > | > | Tried this already (see att

Re: M4 1.4.10b [beta] released

n for reporting this hot spot in execution, and forcing me to come up with a nicer way to optimize it. http://git.sv.gnu.org/gitweb/?p=m4.git;a=commitdiff;h=7468916 - -- Don't work too hard, make some time for fun as well! Eric Blake [EMAIL PROTECTED] -BEGIN PGP SIGNATURE--

Re: M4 1.4.10b [beta] released

hat memchr is prototyped to return void* instead of char*. - -- Don't work too hard, make some time for fun as well! Eric Blake [EMAIL PROTECTED] -BEGIN PGP SIGNATURE- Version: GnuPG v1.4.5 (Cygwin) Comment: Public key at home.comcast.net/~ericblake/eblake.gpg Comment: Us

Re: M4 1.4.10b [beta] released

Eric Blake byu.net> writes: > | That cast looks unnecessary -- unless you care about C++ compilers. > > Yes, at one point, I got M4 to compile with C++; I've tried to keep it > that way (although inadvertent regressions may have crept in since). In > other words, I delib

m4-1.4.11 released

rerun the `gpg --verify' command. This release was bootstrapped with the following tools: ~ Autoconf 2.61 ~ Automake 1.10.1 ~ Gnulib v0.0-433-g2ada70a ../NEWS * Noteworthy changes in Version 1.4.11 (2008-04-02) [stable] ~ Released by Eric Blake, based on git version 1.4.10a ** Security

Re: m4-1.4.11 released

his email if you wish - but | please strip my email address from it first (I don't use a | spam filter). | - -- Don't work too hard, make some time for fun as well! Eric Blake [EMAIL PROTECTED] -BEGIN PGP SIGNATURE- Version: GnuPG v1.4.9 (Cygwin) Comment: Public

  1   2   3   >