From: David Presotto <presotto@closedmind.org>
To: 9fans@cse.psu.edu
Subject: Re: [9fans] COND LIST on vlong
Date: Fri, 5 Mar 2004 08:50:46 -0500 [thread overview]
Message-ID: <e31d70e71898a21aa97ded3dac178340@plan9.bell-labs.com> (raw)
In-Reply-To: <200403051345.i25Dj5CJ009753@adat.davidashen.net>
[-- Attachment #1: Type: text/plain, Size: 185 bytes --]
I'm assuming that by COMMA you mean expressions separated by
COMMAs? If so, that is supported. I thought you meant vlong
comma separated expressions or is that really what you mean?
[-- Attachment #2: Type: message/rfc822, Size: 2626 bytes --]
From: David Tolpin <dvd@davidashen.net>
To: 9fans@cse.psu.edu
Subject: Re: [9fans] COND LIST on vlong
Date: Fri, 5 Mar 2004 17:45:05 +0400 (AMT)
Message-ID: <200403051345.i25Dj5CJ009753@adat.davidashen.net>
> Its clearly an omission and I know that ken intended it. Is that
> what you're asking?
>
graphviz has a package tools/sfio which is of not much use under
plan9 (and not used by basic graphviz tools), but which macros
rely heavily on COMMA.
If not supporting COMMA is phisolophy, I will be trying to rewrite
those macros to compile, but there are really a lot things to change.
If it is an omission, I can leave sfio out of the port and write
a comment about it in hope it will be implemented sometimes in
the future.
David
next prev parent reply other threads:[~2004-03-05 13:50 UTC|newest]
Thread overview: 12+ messages / expand[flat|nested] mbox.gz Atom feed top
2004-03-05 13:25 David Tolpin
2004-03-05 13:40 ` David Presotto
2004-03-05 13:45 ` David Tolpin
2004-03-05 13:50 ` David Presotto [this message]
2004-03-05 13:54 ` David Tolpin
2004-03-05 13:58 ` David Presotto
2004-03-05 13:55 ` dbailey27
2004-03-05 14:13 ` boyd, rounin
2004-03-05 14:21 ` C H Forsyth
2004-03-05 14:03 ` David Tolpin
2004-03-06 10:43 ` Bruce Ellis
2004-03-05 17:00 ` Russ Cox
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=e31d70e71898a21aa97ded3dac178340@plan9.bell-labs.com \
--to=presotto@closedmind.org \
--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).