Bruno,
Hi. I forgot to mention that you should use the dfa.[ch] in the gawk-stable
CVS on Savannah. This is the most up to date version.
Thanks!
Arnold
On Mon, 02. Feb 2009, 22:27:03 +0100, Paolo Bonzini wrote:
> > Simon, Paolo, do you have any comments on the patches suggested in this
> > thread?
>
> I didn't see anything wrong -- on the contrary. If you resend it, I'll
> apply it.
OK, I resend the part that I wrote (provide POSIX semantics fo
Bruno,
Hi. This all sounds fine. I really appreciate your taking this on.
If you are very Strong In The Force, there are also bugs in dfa.c
that "someone" should eventually tackle. The biggest has to do with
the handling of x{0}.
If not, that's OK too - what you're doing is a definite step for
Simon Josefsson wrote:
> >>> printf can fail for reasons like ENOMEM ...
> >>
> >> Does this problem occur in practice on any modern platform?
> >
> > ... the failure scenario is
> > more likely to occur when using formats that produce lots of output (large
> > precisions), or convert floating poi
Is this something the gnulib printf module can detect and work around?
Yeah, exactly! Would be much better than rewriting the world.
(Sorry for my duplicate mail earlier, I hadn't seen Simon's msg yet.)
I really like seeing the <> around URLs in a text format;
I hate it, but we've already concluded we're doing it, so fine :).
I've never had trouble understanding whether a trailing period in text
is part of the url (it isn't), and the simple software I use
(browse-url-at-point, basically) do
> Simon, Paolo, do you have any comments on the patches suggested in this
> thread?
I didn't see anything wrong -- on the contrary. If you resend it, I'll
apply it.
Paolo
It's a one-character addition (plus a gnulib module) to use xprintf
everywhere you used to use printf
Sure. But virtually every program, GNU or otherwise, uses printf.
Before we change/recommend changing all the source files in the world,
my question is, do the common implementations such
Sylvain Beucler writes:
> Hi,
>
> I'm trying to implement simply a '--with-mylib=/path/to/mylib' option
> in 'configure', and I'm wondering if the 'havelib' would help.
Hi. I believe it does.
> However I don't really understand how it's meant to be
> used. Apparently its m4 macros need to be u
Hi,
I'm trying to implement simply a '--with-mylib=/path/to/mylib' option
in 'configure', and I'm wondering if the 'havelib' would help.
However I don't really understand how it's meant to be
used. Apparently its m4 macros need to be used within a macro
definition?
Can you explain me basically w
On Fri, 26. Dec 2008, 01:35:46 +0100, Bruno Haible wrote:
> > Here's an updated
> > patch. I used memcpy() because POSIX requires silent truncation of the
> > option value in case optlen is smaller than necessary.
>
> Looks all fine to me, but it's Simon and Paolo who have to decide on this.
>
>
Eric Blake writes:
> According to Simon Josefsson on 2/2/2009 5:16 AM:
>>> In m4, I was using xprintf instead of printf. Is it worth the extra
>>> security here? printf can fail for reasons like ENOMEM which do not set
>>> the ferror flag and thus are not caught by the close_stdout atexit modul
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
According to Simon Josefsson on 2/2/2009 5:16 AM:
>> In m4, I was using xprintf instead of printf. Is it worth the extra
>> security here? printf can fail for reasons like ENOMEM which do not set
>> the ferror flag and thus are not caught by the clos
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
According to Jim Meyering on 1/30/2009 11:51 AM:
>>
>> 1) The two above aren't sentences.
>> 2) Adding punctuation around url's just makes them more painful to cut
>>and paste. It's easiest when it's bare text at the end of a line.
>>
>
> I too h
Eric Blake writes:
> According to Simon Josefsson on 1/22/2009 3:29 AM:
>> +
>> +void
>> +emit_bug_reporting_address (void)
>> +{
>> + /* TRANSLATORS: The placeholder indicates the bug-reporting address
>> + for this package. Please add _another line_ saying
>> + "Report translation bug
Jim Meyering writes:
> Simon Josefsson wrote:
>> Jim Meyering writes:
>>> Mark McLoughlin noticed that the getaddrinfo test fails
>>> when there's no network, and sent the patch below.
>>>
>>> This looks like a good idea.
>>> Though maybe we should make it skip the test (return 77) after saying
16 matches
Mail list logo
