From: Kevin Ryde <user42@zip.com.au>
Subject: Re: extending FEM enginering package with Guile
Date: Wed, 07 Jan 2004 08:31:39 +1000 [thread overview]
Message-ID: <87fzes90ac.fsf@zip.com.au> (raw)
In-Reply-To: <200401061935.i06JZtU3003103@minerva.ceride.gov.ar> (Mario Storti's message of "Tue, 06 Jan 2004 16:35:55 -0300")
Mario Storti <mstorti@intec.unl.edu.ar> writes:
>
> So I have now a working `while-continue-break' macro. This
> is a warkaround until a new stable release comes out.
There are no plans to change `while' in the 1.6 branch. Certainly
continue is broken, but it wasn't documented, so doesn't really
qualify for a bug fix.
_______________________________________________
Guile-user mailing list
Guile-user@gnu.org
http://mail.gnu.org/mailman/listinfo/guile-user
next prev parent reply other threads:[~2004-01-06 22:31 UTC|newest]
Thread overview: 10+ messages / expand[flat|nested] mbox.gz Atom feed top
2004-01-06 19:35 extending FEM enginering package with Guile Mario Storti
2004-01-06 22:31 ` Kevin Ryde [this message]
-- strict thread matches above, loose matches on Subject: below --
2004-01-05 19:20 Mario Storti
2004-01-05 20:26 ` Paul Jarc
2004-01-05 21:32 ` Ken Anderson
2004-01-05 22:04 ` rm
2004-01-08 4:58 ` Keith Wright
2004-01-08 6:04 ` Paul Jarc
2004-01-08 22:13 ` Keith Wright
2004-01-09 21:31 ` Keith Wright
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
List information: https://www.gnu.org/software/guile/
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=87fzes90ac.fsf@zip.com.au \
--to=user42@zip.com.au \
/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).