ntg-context - mailing list for ConTeXt users
 help / color / mirror / Atom feed
From: luigi scarso <luigi.scarso@gmail.com>
To: mailing list for ConTeXt users <ntg-context@ntg.nl>
Subject: Re: Suggestion
Date: Fri, 19 Jun 2009 09:33:28 +0200	[thread overview]
Message-ID: <fe8d59da0906190033id8178a9p6d6ac04d001c67a6@mail.gmail.com> (raw)
In-Reply-To: <68bfdc900906190006t4e9ad352l94d4d99c8d69e83d@mail.gmail.com>


[-- Attachment #1.1: Type: text/plain, Size: 2167 bytes --]

On Fri, Jun 19, 2009 at 9:06 AM, Yue Wang <yuleopen@gmail.com> wrote:

> On Fri, Jun 19, 2009 at 2:29 PM, luigi scarso<luigi.scarso@gmail.com>
> wrote:
> >>
> >> Anyway, I highly respect the ConTeXt and LuaTeX's work.
> >> But if Taco and Hans can :
> >>
> >> - use a proper regexp library (like lrexlib?), not the silly lpeg
> >
> > PEG are not silly at all. PEG *include* regex, but not viceversa,
> > and it seems to have the same power of  CFG, so you can build a parser
> for
> > pratically anything
> > (and you can not do this with regex) .
> > Perhaps the reverse sentence has more sense: drop the "silly" (?) regex,
> use
> > the new peg.
> > For what I know the reverse side of lpeg is that a file must be loaded in
> > memory completly.
>
> Well, I don't like to know what kind of thing is superior ... micro
> kernel is superior than monolithic kernel, but...
>
Wrong paragon .
>From *mathematical*  point  of  view, the set of all regular languages
are a subset of PEG languages .
PEG are more powerful than  regex --it's not an opinion, it's a fact.


> The key reason for this is, more people are familiar with regexp. so
> if you can build a 100% compatible regexp module on top of lpeg in
> ConTeXt, it will be ok, or even better...
>
We already have lua for simple string manipulation, and lpeg for other
stuffs .
Again we don't need regex .


> >
> >> - full support of xslt:)
> >
> > why not xquery too? Are mkiv  supposed to be a full  xml processor ?
>
>
> No. I mean the user can have an option to convert an xml (that is, a
> context document) using (maybe external) xslt tool.
> This won't be too difficult to implement ...
>
hmm, external tools call for platform /SO issue ...
Personally xsltproc in linux it's OK -- I don't need
an integration ,
I prefear separations of concerns.



>
> > A bit of xslt can be done with lpeg (and not regex),
>
> a bit == far from all
>
It's enough for simple xml processing .
If you need more, are you sure that you are using  the right tool ?



>
> >> Things might be a lot better...
> >
> > and worse too .
> > Things are now a lot better than before ,IMMO .
> >
>
> it should be.
>

It is .
-- 
luigi

[-- Attachment #1.2: Type: text/html, Size: 3597 bytes --]

[-- Attachment #2: Type: text/plain, Size: 487 bytes --]

___________________________________________________________________________________
If your question is of interest to others as well, please add an entry to the Wiki!

maillist : ntg-context@ntg.nl / http://www.ntg.nl/mailman/listinfo/ntg-context
webpage  : http://www.pragma-ade.nl / http://tex.aanhet.net
archive  : https://foundry.supelec.fr/projects/contextrev/
wiki     : http://contextgarden.net
___________________________________________________________________________________

  reply	other threads:[~2009-06-19  7:33 UTC|newest]

Thread overview: 26+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2009-06-15 11:55 Suggestion Arun Dev
2009-06-16  7:42 ` Suggestion R. Bastian
2009-06-16  7:50   ` Suggestion Taco Hoekwater
2009-06-19  3:55 ` Suggestion Yue Wang
2009-06-19  6:29   ` Suggestion luigi scarso
2009-06-19  7:06     ` Suggestion Yue Wang
2009-06-19  7:33       ` luigi scarso [this message]
2009-06-19  9:23       ` Suggestion Arthur Reutenauer
     [not found] <Your message of "Sun, 27 Jan 2002 19:02:33 +0100." <5.1.0.14.1.20020127190025.02af2008@server-1>
2002-01-28 10:59 ` suggestion Patrick Gundlach
2002-01-28 12:01   ` suggestion Hans Hagen
2002-01-28 12:33   ` suggestion Hans Hagen
2002-01-28 12:40   ` suggestion Taco Hoekwater
2002-01-28 12:48   ` suggestion Eckhart Guthöhrlein
2002-01-28 13:02   ` suggestion Eckhart Guthöhrlein
2002-01-28 13:44     ` suggestion Hans Hagen
2002-01-28 21:28   ` suggestion Daniel Pittman
  -- strict thread matches above, loose matches on Subject: below --
2002-01-25 13:07 suggestion Hans Hagen
2002-01-25 14:23 ` suggestion Berend de Boer
2002-01-25 18:03   ` suggestion Frans Goddijn
2002-01-25 18:36   ` suggestion Eckhart Guthöhrlein
2002-01-25 18:46     ` suggestion Frans Goddijn
2002-01-27 18:02       ` suggestion Hans Hagen
2002-01-25 22:47 ` suggestion Daniel Pittman
2000-11-03 23:06 suggestion Denis B. Roegel
1999-06-01 19:04 Suggestion David Arnold
1999-06-02  7:22 ` Suggestion Hans Hagen

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

* Reply using the --to, --cc, and --in-reply-to
  switches of git-send-email(1):

  git send-email \
    --in-reply-to=fe8d59da0906190033id8178a9p6d6ac04d001c67a6@mail.gmail.com \
    --to=luigi.scarso@gmail.com \
    --cc=ntg-context@ntg.nl \
    /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 NNTP newsgroup(s).