|TWIG any info firstname.lastname@example.org (1996-05-14)|
|Re: TWIG any info email@example.com (1996-05-19)|
|Re: TWIG any info Peter.Damron@Eng.Sun.COM (1996-05-19)|
|Re: TWIG any info firstname.lastname@example.org (1996-05-19)|
|Re: TWIG any info email@example.com (1996-05-21)|
|Re: TWIG any info firstname.lastname@example.org (David Hanson) (1996-05-24)|
|Re: TWIG any info email@example.com (1996-05-24)|
|From:||firstname.lastname@example.org (David Chase)|
|Date:||21 May 1996 16:18:19 -0400|
email@example.com () writes:
> TWIG code generator generator using tree pattern matching/rewriting.
> Can anybody give links to TWIG ? Where is it available
> source/binary form / at what terms/conditions for non-commercial use.
You'd probably be better off with either burg, or iburg. Iburg is most like
twig, algorithmically speaking. Burg generates faster matchers, but you
don't have as much freedom in figuring out the costs at runtime (as in, none
-- costs for patterns must be statically assigned). I think the consensus
of the people who build and use these things is that iburg's algorithm is
the one most people should use, except for applications in which speed of
code generation is extraordinarily important. (Note that I am explicitly
un-tooting my own horn here; years ago I made a decent contribution to the
technology used in burg, but I think you'd be better off with iburg. In my
own work, I would always use iburg first, and only consider burg after I had
measured the time spent generating code and found it too costly.)
My copy of iburg says:
iburg is available for anonymous ftp from ftp.cs.princeton.edu
(18.104.22.168) in pub/iburg.tar.Z or pub/iburg.zip.
Here's the iburg copyright:
Copyright (C) 1993 David R. Hanson
All Rights Reserved.
Iburg is protected by copyright. It is not public-domain software,
shareware, and it is not protected by a ``copyleft'' agreement, like
the code from the Free Software Foundation.
Iburg is available free for your personal research and instructional
use under the ``fair use'' provisions of the copyright law.
You may not sell iburg or any product derived from it in which iburg is
a significant part of the value of the product. You may use the output
from iburg in products as long as you charge for only those components
that are entirely your own and you acknowledge the use of iburg clearly
in all product documentation and distribution media. You must also
request that bug reports on your product be reported to you.
My understanding of this copyright is that if you want to use iburg
to build the code generator for a compiler ("the output from iburg")
you wish to sell, provided that you comply with some simple and
non-onerous rules ("as long as ...."). I also suspect that the author
of iburg is a reasonable person, who'd be willing to explain his
intentions here in more detail if you had specific questions.
[Dave Hanson is indeed an entirely reasonable guy, I knew him when he was at
Yale years ago. -John]
Return to the
Search the comp.compilers archives again.