Re: re-search-forward ... nil t) results in error instead of returningnil

[Luc Teirlinck]

"Drew Adams" <address@hidden> wrote:

   Currently, the doc suggests (to me, anyway) that the "no-fail" arg
   causes the function to return nil in case of _failure_ (and it speaks
   specifically of _error_)

It speaks specifically of `error' in the sense or returning nil
instead of throwing an error in case of _failure_.  Failure in this
context means search failure:

     "Optional third argument, if t, means if fail just return nil (no error).


   You mention the REPEAT arg, but I don't believe that that has anything to do
   with this - the REPEAT arg was nil in this test.

I guess you mean:

   Note that REPEAT determines what happens if the function `fails',

Sorry, that was a typo.  I meant:

   Note that NOERROR determines what happens if the function `fails',

       By the way, I _can_ reproduce this if I first execute:
       ulimit -s 8192
       before I do `emacs -q'.

   Sounds like that is an answer to my question of how to increase the stack
   size - for Unix/Linux. Do you know how to do it on Windows?

No.  I do not use MS Windows.  Also, you might need certain priviliges
to get past the _hard_ limit, if there is such a thing on MS Windows.

In as far as possible performance degradation vs Emacs 20 is
concerned, let us wait till Stefan Monnier reads this, since
MAINTAINERS lists him as maintainer for `src/regex.c'.  I personally
am not familiar with the details.

Sincerely,

Luc.