From: David Tolpin <dvd@davidashen.net>
To: 9fans@cse.psu.edu
Subject: Re: [9fans] graphviz-1.10 port
Date: Mon, 8 Mar 2004 10:12:48 +0400 [thread overview]
Message-ID: <200403080612.i286CmXb083675@adat.davidashen.net> (raw)
In-Reply-To: <7a682bfdaa722f04b826e3b3851a7a28@plan9.ucalgary.ca>
> > Now, when the code is working, either the poster of the remark,
> > or any other volunteer, is welcome to re-arrange and rewrite the
> > make process.
>
> the code isn't working.
Only because you run 'make clean'. graphviz distribution includes
scan.c generated from scan.l (from research.att.com, not my port),
because scan.l requires flex, not lex. Should I rewrite scan.l
in lex too?
> secondly you replace:
In what respect will it make the program better?
next prev parent reply other threads:[~2004-03-08 6:12 UTC|newest]
Thread overview: 78+ messages / expand[flat|nested] mbox.gz Atom feed top
2004-03-05 22:23 David Tolpin
2004-03-05 23:06 ` boyd, rounin
2004-03-08 4:40 ` Kenji Okamoto
2004-03-08 4:55 ` boyd, rounin
2004-03-08 5:04 ` Kenji Okamoto
2004-03-08 5:09 ` boyd, rounin
2004-03-08 5:18 ` Kenji Okamoto
2004-03-08 5:21 ` Kenji Okamoto
2004-03-08 5:30 ` boyd, rounin
2004-03-08 5:48 ` David Tolpin
2004-03-08 5:08 ` andrey mirtchovski
2004-03-08 6:02 ` dbailey27
2004-03-08 6:12 ` David Tolpin [this message]
2004-03-08 6:11 ` dbailey27
2004-03-08 5:32 ` andrey mirtchovski
2004-03-08 6:19 ` David Tolpin
2004-03-08 8:45 ` Charles Forsyth
2004-03-08 6:16 ` David Tolpin
2004-03-08 8:33 ` Charles Forsyth
2004-03-08 4:59 ` boyd, rounin
2004-03-08 5:07 ` George Michaelson
2004-03-08 5:31 ` David Tolpin
2004-03-08 4:51 ` andrey mirtchovski
2004-03-08 6:14 ` David Tolpin
2004-03-08 6:23 ` Kenji Okamoto
2004-03-08 6:25 ` David Tolpin
2004-03-08 8:31 ` Charles Forsyth
2004-03-08 8:37 ` David Tolpin
2004-03-08 8:39 ` Charles Forsyth
2004-03-08 10:05 ` Geoff Collyer
2004-03-08 4:55 ` andrey mirtchovski
2004-03-08 6:16 ` David Tolpin
2004-03-08 5:25 ` andrey mirtchovski
2004-03-08 6:30 ` Kenji Okamoto
2004-03-08 5:44 ` andrey mirtchovski
2004-03-08 6:46 ` Kenji Okamoto
2004-03-08 9:22 ` 9nut
2004-03-08 8:24 ` Fco.J.Ballesteros
2004-03-08 8:51 ` Kenji Okamoto
2004-03-08 8:49 ` Kenji Okamoto
2004-03-08 9:20 ` 9nut
2004-03-08 8:28 ` lucio
2004-03-08 13:01 ` boyd, rounin
2004-03-08 19:25 ` Derek Fawcus
2004-03-08 20:21 ` Axel Belinfante
2004-03-08 20:26 ` Axel Belinfante
2004-03-08 20:40 ` boyd, rounin
2004-03-08 22:40 ` 9nut
2004-03-08 21:20 ` Derek Fawcus
2004-03-08 22:24 ` Wes Kussmaul
2004-03-09 9:24 ` Charles Forsyth
2004-03-09 1:51 ` Kenji Okamoto
2004-03-05 22:30 David Tolpin
2004-03-06 1:47 ` David Presotto
2004-03-06 6:23 ` David Tolpin
2004-03-08 8:38 Tiit Lankots
2004-03-08 8:41 ` lucio
2004-03-08 8:56 ` Kenji Okamoto
2004-03-08 9:17 ` Kenji Okamoto
2004-03-08 9:22 ` lucio
2004-03-08 13:08 ` boyd, rounin
2004-03-08 13:07 ` boyd, rounin
2004-03-08 8:49 Tiit Lankots
2004-03-08 8:53 Tiit Lankots
2004-03-08 9:28 Keith Nash
2004-03-08 13:10 ` boyd, rounin
2004-03-08 13:44 Noah Evans
2004-03-08 14:09 ` Gorka Guardiola Múzquiz
2004-03-08 14:13 ` David Presotto
2004-03-08 14:46 ` boyd, rounin
2004-03-08 14:45 ` boyd, rounin
2004-03-09 1:29 ` Kenji Okamoto
2004-03-08 16:22 ` boyd, rounin
2004-03-08 16:40 ` imp123
2004-03-08 14:20 Noah Evans
2004-03-08 16:39 Noah Evans
2004-03-08 16:50 ` boyd, rounin
2004-03-08 16:57 Noah Evans
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=200403080612.i286CmXb083675@adat.davidashen.net \
--to=dvd@davidashen.net \
--cc=9fans@cse.psu.edu \
/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).