From: Matt Wette <matt.wette@gmail.com>
To: Matt Wette <matt.wette@gmail.com>
Cc: guile-user@gnu.org
Subject: Re: Nyacc patches for Mes to avoid bundling?
Date: Thu, 4 May 2017 19:09:22 -0700 [thread overview]
Message-ID: <20B29595-EC72-4660-815A-0261AD88B519@gmail.com> (raw)
In-Reply-To: <1B4686A9-DAC0-4DD4-B11B-78629E0C5339@gmail.com>
> On May 3, 2017, at 5:07 PM, Matt Wette <matt.wette@gmail.com> wrote:
>
>
>> On May 3, 2017, at 10:59 AM, Jan Nieuwenhuizen <janneke@gnu.org> wrote:
>>
>> Hi Matt,
>>
>> Mes is now packaged in Guix. It bundles a modified copy of
>> Nyacc-0.76.5. It would like to package Nyacc separately and
>> depend on that, however, Mes cannot use Nyacc as is, at the
>> moment because of three Mes problems
>>
>> 1) Mes has no regex
>> 2) Mes has no proper module system, there is only one environment
>> 3) For Mes I like simple pmatch better than match
>>
>> Attached are the patches Mes is using right now. I intend to fix 2) at
>> a certain point but haven't planned that yet. I have no plans for 1),
>> I'd rather not support regexps if I can get away with it. 3) is
>> probably not mandatory, but it helps being lightweight.
>>
>> How do you feel about supporting such shortcomings of Mes? I can
>> imagine that's not a great thing to do, however Mes carrying a copy
>> of Nyacc is also not fantastic?
>>
>> Greetings,
>> janneke
>
> Hi Jan,
>
> Those don’t look to terrible to do. I will take a look. I think they can be done.
But it would be nice to know what MES does have. String-search ? Character sets?
I have replaced match w/ pmatch .
next prev parent reply other threads:[~2017-05-05 2:09 UTC|newest]
Thread overview: 23+ messages / expand[flat|nested] mbox.gz Atom feed top
2017-05-03 17:59 Nyacc patches for Mes to avoid bundling? Jan Nieuwenhuizen
2017-05-04 0:07 ` Matt Wette
2017-05-05 2:09 ` Matt Wette [this message]
2017-05-05 6:07 ` Jan Nieuwenhuizen
2017-05-05 12:44 ` Matt Wette
2017-05-05 13:33 ` Jan Nieuwenhuizen
2017-05-05 22:59 ` Matt Wette
2017-05-06 15:21 ` Matt Wette
2017-05-06 16:00 ` Jan Nieuwenhuizen
2017-05-06 16:21 ` Matt Wette
2017-05-06 16:33 ` Jan Nieuwenhuizen
2017-05-07 7:54 ` Jan Nieuwenhuizen
2017-05-07 14:16 ` Matt Wette
2017-05-08 15:37 ` Jan Nieuwenhuizen
2017-05-10 21:01 ` Jan Nieuwenhuizen
2017-05-11 0:21 ` Matt Wette
2017-05-12 3:52 ` Matt Wette
2017-05-12 6:00 ` Jan Nieuwenhuizen
2017-05-12 15:10 ` Matt Wette
2017-05-05 13:19 ` Ludovic Courtès
2017-05-05 19:56 ` Jan Nieuwenhuizen
2017-05-05 20:22 ` Ludovic Courtès
2017-05-06 15:49 ` Jan Nieuwenhuizen
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
List information: https://www.gnu.org/software/guile/
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=20B29595-EC72-4660-815A-0261AD88B519@gmail.com \
--to=matt.wette@gmail.com \
--cc=guile-user@gnu.org \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for read-only IMAP folder(s) and NNTP newsgroup(s).