bug-zile
[Top][All Lists]
Advanced

[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]

Re: [Bug-zile] Zile Lua: Gary, please feel free to look after the branch


From: Gary V. Vaughan
Subject: Re: [Bug-zile] Zile Lua: Gary, please feel free to look after the branch for now
Date: Tue, 9 Aug 2011 21:43:15 +0700

Hi Brian,

On 9 Aug 2011, at 20:19, Brian Maher wrote:
> On Wed, Aug 3, 2011 at 10:50 PM, Gary V. Vaughan <address@hidden> wrote:
>> On 4 Aug 2011, at 11:38, Brian Maher wrote:
>>> On Sat, Jul 30, 2011 at 9:58 PM, Gary V. Vaughan <address@hidden> wrote:
>>>>  - replacing lrex-gnu with LPEG's re module;
>>>>    Obviously this breaks emacs compatibility, but GNU regex is huge and
>>>>    lrex in general is still a source of build problems for me.
>>> 
>>> FWIW, lrex-gnu didn't build on OS X...
>> 
>> It can be built on OS X, but you have to do it all manually from the command
>> line, which is no fun at all :(
> 
> I prefer to build from the command line :)

Well sure, but not when you have to write the gcc commands by hand for each
stage of the link!

>> The trick is to manually build a libgnu.a from -fpic objects of regex.o and
>> supporting files from a recent gnulib clone, extract those objects from the
>> archive into the lrex_gnu directory, and then create a shared library from
>> them and the objects from lrex_gnu itself.  It's painful and error prone
>> but can be done.  Ping me if you'd like me to look up the recipe I used in
>> my shell history.
> 
> Ya, I'm interested... perhaps you could check-in your script complete
> with a curl command to download gnulib?

It's scrolled out of my history already, but I'll recreate it when I get a
moment later in the week - especially if you harass me about it :)

> IMHO, the biggest problem I've ran into with Lua regexps is the lack
> of supporting "|"... I know I can work around this problem by matching
> multiple regexps against the same string, but it is a PITA, especially
> if you want to put a regex in a config or other places where you
> expect to only specify a single regex.

Agreed.  That's why I expect to need LPEGs too, though a lighter build
with only native expressions will work in the absence of the LPEG library.

>>> I can't comment on using LPEG's re module since I don't have
>>> experience with that, but something more like PCRE would be a welcome
>>> change to me :-).
>> 
>> On reflection, it ought not to be much of a problem to add a configure
>> switch that allows Zile to use PCRE rather than GNU regexps... care to
>> submit a patch?
> 
> Sure, I've attached the patch.

Thanks, I'll try and get lrex-pcre compiled to test it, and then commit :)

> FWIW, I've also got a patch to make it
> easier to get stack traces if zile crashes:

Nice, that seems saner than the shell wrapper I've been using:

  zile ()
  {
    zile ${1+"$@"} 2> /tmp/zile$$.log || cat /tmp/zile$$.log
  }

Applied!

Cheers,
-- 
Gary V. Vaughan (gary AT gnu DOT org)


reply via email to

[Prev in Thread] Current Thread [Next in Thread]