From mboxrd@z Thu Jan 1 00:00:00 1970 X-Msuck: nntp://news.gmane.io/gmane.comp.tex.context/51370 Path: news.gmane.org!not-for-mail From: luigi scarso Newsgroups: gmane.comp.tex.context Subject: Re: Suggestion Date: Fri, 19 Jun 2009 09:33:28 +0200 Message-ID: References: <9028d48b0906150455y389713fdo42932d9b2492ed70@mail.gmail.com> <68bfdc900906182055w69ca488m9ddcf0f13bb452b3@mail.gmail.com> <68bfdc900906190006t4e9ad352l94d4d99c8d69e83d@mail.gmail.com> Reply-To: mailing list for ConTeXt users NNTP-Posting-Host: lo.gmane.org Mime-Version: 1.0 Content-Type: multipart/mixed; boundary="===============0987095333==" X-Trace: ger.gmane.org 1245396866 6728 80.91.229.12 (19 Jun 2009 07:34:26 GMT) X-Complaints-To: usenet@ger.gmane.org NNTP-Posting-Date: Fri, 19 Jun 2009 07:34:26 +0000 (UTC) To: mailing list for ConTeXt users Original-X-From: ntg-context-bounces@ntg.nl Fri Jun 19 09:34:24 2009 Return-path: Envelope-to: gctc-ntg-context-518@m.gmane.org Original-Received: from ronja.vet.uu.nl ([131.211.172.88] helo=ronja.ntg.nl) by lo.gmane.org with esmtp (Exim 4.50) id 1MHYcC-0004RC-DM for gctc-ntg-context-518@m.gmane.org; Fri, 19 Jun 2009 09:34:24 +0200 Original-Received: from localhost (localhost [127.0.0.1]) by ronja.ntg.nl (Postfix) with ESMTP id C72861FAD7; Fri, 19 Jun 2009 09:34:22 +0200 (CEST) Original-Received: from ronja.ntg.nl ([127.0.0.1]) by localhost (smtp.ntg.nl [127.0.0.1]) (amavisd-new, port 10024) with LMTP id 05905-02; Fri, 19 Jun 2009 09:33:41 +0200 (CEST) Original-Received: from ronja.vet.uu.nl (localhost [127.0.0.1]) by ronja.ntg.nl (Postfix) with ESMTP id C7F7E1FB30; Fri, 19 Jun 2009 09:33:40 +0200 (CEST) Original-Received: from localhost (localhost [127.0.0.1]) by ronja.ntg.nl (Postfix) with ESMTP id 9300E1FB30 for ; Fri, 19 Jun 2009 09:33:39 +0200 (CEST) Original-Received: from ronja.ntg.nl ([127.0.0.1]) by localhost (smtp.ntg.nl [127.0.0.1]) (amavisd-new, port 10024) with LMTP id 00517-02 for ; Fri, 19 Jun 2009 09:33:30 +0200 (CEST) Original-Received: from filter3-til.mf.surf.net (filter3-til.mf.surf.net [194.171.167.219]) by ronja.ntg.nl (Postfix) with ESMTP id F1AF01FB1F for ; Fri, 19 Jun 2009 09:33:29 +0200 (CEST) Original-Received: from mail-ew0-f228.google.com (mail-ew0-f228.google.com [209.85.219.228]) by filter3-til.mf.surf.net (8.13.8/8.13.8/Debian-3) with ESMTP id n5J7XSSH016782 for ; Fri, 19 Jun 2009 09:33:29 +0200 Original-Received: by ewy28 with SMTP id 28so2020707ewy.2 for ; Fri, 19 Jun 2009 00:33:28 -0700 (PDT) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=gamma; h=domainkey-signature:mime-version:received:in-reply-to:references :date:message-id:subject:from:to:content-type; bh=a2p0vtdOvJBK5QFs8vSSuIrXe1sGdB/H90hzDtBFGkk=; b=wObAY82LAw1QAEjwhFCeleAnfyuW80xtOlOrrgBqsHfa8Qy6V2qvPjXG0A3f7/7JV8 alYCasb5SmQUqO1YI8ABwKySuOrjBiss36734F1Ya8WFq/9a6sLt/iO2kd2UqcavXo/r kV5GntExg3uyAKHGa4Ehz5FiIVW0+03BS9bNs= DomainKey-Signature: a=rsa-sha1; c=nofws; d=gmail.com; s=gamma; h=mime-version:in-reply-to:references:date:message-id:subject:from:to :content-type; b=odl5rPxZlmEFE1f/zdQ4C5v3XS0BAl+H/d1KzGX3ThQEdJ0u7N8Mv0VPog1DQhb8zr 1A71mtrxCNM1t6e1/6JnpUhJI2OcsQ1h05KXLhg/XYBRicVVracAxcWyFyYEvU5MV1Zt s3f3EQwa7jHLqufswcayIzEIvOwIEovofPkz4= Original-Received: by 10.216.18.205 with SMTP id l55mr900528wel.194.1245396808457; Fri, 19 Jun 2009 00:33:28 -0700 (PDT) In-Reply-To: <68bfdc900906190006t4e9ad352l94d4d99c8d69e83d@mail.gmail.com> X-Bayes-Prob: 0.0001 (Score 0, tokens from: @@RPTN) X-CanIt-Geo: ip=209.85.219.228; country=US; region=CA; city=Mountain View; postalcode=94043; latitude=37.4192; longitude=-122.0574; metrocode=807; areacode=650; http://maps.google.com/maps?q=37.4192,-122.0574&z=6 X-CanItPRO-Stream: uu:ntg-context@ntg.nl (inherits from uu:default, base:default) X-Canit-Stats-ID: 245979082 - e17bebee2e1a - 20090619 X-Scanned-By: CanIt (www . roaringpenguin . com) on 194.171.167.219 X-Virus-Scanned: amavisd-new at ntg.nl X-BeenThere: ntg-context@ntg.nl X-Mailman-Version: 2.1.11 Precedence: list List-Id: mailing list for ConTeXt users List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , Original-Sender: ntg-context-bounces@ntg.nl Errors-To: ntg-context-bounces@ntg.nl X-Virus-Scanned: amavisd-new at ntg.nl Xref: news.gmane.org gmane.comp.tex.context:51370 Archived-At: --===============0987095333== Content-Type: multipart/alternative; boundary=0016e64c27405f5e7b046cae8aeb --0016e64c27405f5e7b046cae8aeb Content-Type: text/plain; charset=UTF-8 Content-Transfer-Encoding: 7bit On Fri, Jun 19, 2009 at 9:06 AM, Yue Wang wrote: > On Fri, Jun 19, 2009 at 2:29 PM, luigi scarso > 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 --0016e64c27405f5e7b046cae8aeb Content-Type: text/html; charset=UTF-8 Content-Transfer-Encoding: quoted-printable

On Fri, Jun 19, 2009 at 9:06 AM, Yue Wan= g <yuleopen@gmai= l.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<= br> >
> PEG are not silly at all. PEG *include* regex, but not viceversa,
> and it seems to have the same power of=C2=A0 CFG, so you can build a p= arser 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 ... mic= ro
kernel is superior than monolithic kernel, but...
Wrong paragon .
From *mathematical*=C2=A0 point=C2=A0 = of=C2=A0 view, the set of all regular languages
are a subset of PEG lang= uages .
PEG are more powerful than=C2=A0 regex --it's not an opinio= n, 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 st= ring manipulation, and lpeg for other stuffs .
Again we don't need r= egex .


>
>> - full support of xslt:)
>
> why not xquery too? Are mkiv=C2=A0 supposed to be a full=C2=A0 xml pro= cessor ?


No. I mean the user can have an option to convert an xml (that is, a<= br> context document) using (maybe external) xslt tool.
This won't be too difficult to implement ...
hmm, external tools call for plat= form /SO issue ...
Personally xsltproc in linux it's OK -- I don'= ;t need
an integration ,
I prefear separations of concerns.

=C2=A0

> A bit of xslt can be done with lpeg (and not regex),

a bit =3D=3D far from all
It's enough for simple xml pr= ocessing .
If you need more, are you sure that you are using=C2=A0 the r= ight tool ?

=C2=A0

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

it should be.

It is .
--
luigi

--0016e64c27405f5e7b046cae8aeb-- --===============0987095333== Content-Type: text/plain; charset="us-ascii" MIME-Version: 1.0 Content-Transfer-Encoding: 7bit Content-Disposition: inline ___________________________________________________________________________________ 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 ___________________________________________________________________________________ --===============0987095333==--