unofficial mirror of guile-devel@gnu.org 
 help / color / mirror / Atom feed
From: Bruno Haible <bruno@clisp.org>
To: guile-devel@gnu.org
Subject: goops web page
Date: Tue, 20 Dec 2011 22:53:56 +0100	[thread overview]
Message-ID: <201112202253.56464.bruno@clisp.org> (raw)

Hi,

A web search for guile-oop pointed me to
  http://www.gnu.org/software/goops/
It says:

  "There are plans to merge GOOPS into the Guile distribution."

  "Latest released version is 1.0"

  "Version 1.0 of GOOPS is now available via anonymous FTP as
   http://ftp.gnu.org/gnu/guile/guile-oops-1.0.tar.gz."

  "This release mostly contains adaptations to guile-1.4 and bug fixes."

  "The bleeding edge of development is available via anonymous CVS."

goops is part of the guile 2.0 distribution. This web page appears to be
hopelessly out of date. Why not replace it with a forward to
http://www.gnu.org/software/guile/ ?

Bruno



             reply	other threads:[~2011-12-20 21:53 UTC|newest]

Thread overview: 3+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2011-12-20 21:53 Bruno Haible [this message]
2011-12-21  6:52 ` goops web page Nala Ginrut
2011-12-21 14:58 ` Andy Wingo

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=201112202253.56464.bruno@clisp.org \
    --to=bruno@clisp.org \
    --cc=guile-devel@gnu.org \
    /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).