From: "Frank Ch. Eigler" <fche@redhat.com>
To: Doug Evans <dje@transmeta.com>
Cc: cgen@sources.redhat.com
Subject: Re: guile 1.6 conversion
Date: Tue, 15 Jul 2003 19:05:00 -0000 [thread overview]
Message-ID: <20030715190518.GG10371@redhat.com> (raw)
In-Reply-To: <200307151857.LAA20731@casey.transmeta.com>
[-- Attachment #1: Type: text/plain, Size: 482 bytes --]
Hi -
dje wrote:
> The biggest task in converting to guile 1.6 is handling the
> stricter type checking on string operations. [...]
> Let's keep the notion of being able to freely pass symbols to
> a "string-append"-like function, but just give it a different name
> like strsym-append or some such.
That's fine.
(Can a scheme macro be made conditional on the symbol-ness of its
actual arguments, so that this strsym-append thingie is a macro
rather than a full function?)
- FChE
[-- Attachment #2: Type: application/pgp-signature, Size: 189 bytes --]
prev parent reply other threads:[~2003-07-15 19:05 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2003-07-15 18:57 Doug Evans
2003-07-15 19:05 ` Frank Ch. Eigler [this message]
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=20030715190518.GG10371@redhat.com \
--to=fche@redhat.com \
--cc=cgen@sources.redhat.com \
--cc=dje@transmeta.com \
/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 read-only IMAP folder(s) and NNTP newsgroup(s).