public inbox for cgen@sourceware.org
 help / color / mirror / Atom feed
From: Doug Evans <dje@transmeta.com>
To: cgen@sources.redhat.com
Subject: guile 1.6 conversion
Date: Tue, 15 Jul 2003 18:57:00 -0000	[thread overview]
Message-ID: <200307151857.LAA20731@casey.transmeta.com> (raw)

The biggest task in converting to guile 1.6 is handling the
stricter type checking on string operations.

(string-append "a" 'b)

is ok in guile 1.[34], but not guile 1.6.

It's not portable scheme so we shouldn't do that anyway,
but the simplicity of less stringent type checking in this
particular situation is compelling.

We could go through all of cgen and insert the appropriate
conversions (symbol->string, etc.) but while it may the a correct
thing to do, it's rather cumbersome and the result isn't easy to maintain.

I propose a different solution.
[No claim is made that these are the only solutions.
Other solutions are easily dreamt up at the speed of thought. :-)]

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.
There a handful of other functions involved but you get the idea.

             reply	other threads:[~2003-07-15 18:57 UTC|newest]

Thread overview: 2+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2003-07-15 18:57 Doug Evans [this message]
2003-07-15 19:05 ` Frank Ch. Eigler

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=200307151857.LAA20731@casey.transmeta.com \
    --to=dje@transmeta.com \
    --cc=cgen@sources.redhat.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).