Re: rfc: new __program__ macro

2006-08-04 Thread Eric Blake
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). > > Without it, and due to the fac

verror_r [WAS Re: rfc: new __program__ macro]

2006-08-04 Thread Gary V. Vaughan
Hey Eric! Eric Blake wrote: > 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). Yeah, I saw that thread go by on bug-gnulib. I agree

Re: rfc: new __program__ macro

2006-08-04 Thread Eric Blake
-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 manner that error messages >> d

Re: rfc: new __program__ macro

2006-08-04 Thread Gary V. Vaughan
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 manner that error messages > do? That way, if a user invokes m4 via a symlink or absolute path, rather > than through their PATH, they can match