From: Brian Gough <bjg@gnu.org>
To: Tuomo Keskitalo <Tuomo.Keskitalo@iki.fi>
Cc: Gerard Jungman <jungman@lanl.gov>,
GSL Discuss Mailing List <gsl-discuss@sourceware.org>
Subject: Re: gsl container designs
Date: Thu, 07 Jan 2010 18:29:00 -0000 [thread overview]
Message-ID: <87r5q1vkeb.wl%bjg@network-theory.co.uk> (raw)
In-Reply-To: <4B4477B8.50305@iki.fi>
At Wed, 06 Jan 2010 13:44:56 +0200,
Tuomo Keskitalo wrote:
> Do you mean the compatibility to GSL 1 types by the compatibility cost?
> When talking about GSL 2 I don't think we should give too much value to
> maintaining backwards compatibility. GSL 1 is not going to cease to
> exist, and people who have tied themselves deeply to GSL 1 data
> structures can continue to use it.
I'd say it's a significant benefit if people don't have to modify
their code.
--
Brian Gough
next prev parent reply other threads:[~2010-01-07 18:29 UTC|newest]
Thread overview: 21+ messages / expand[flat|nested] mbox.gz Atom feed top
2009-11-25 0:55 Gerard Jungman
2009-11-29 21:04 ` Brian Gough
2009-12-04 18:48 ` Brian Gough
2009-12-09 21:04 ` using GSL with C++ (was Re: gsl container designs) James Amundson
2009-12-09 21:14 ` Jochen Küpper
2009-12-09 21:54 ` Jari Häkkinen
2009-12-10 11:46 ` Brian Gough
2009-12-10 12:09 ` Brian Gough
2009-12-10 13:42 ` Robert G. Brown
2009-12-10 21:44 ` James Bergstra
2009-12-10 15:15 ` Kevin H. Hobbs
2010-01-06 11:45 ` gsl container designs Tuomo Keskitalo
2010-01-06 15:47 ` Robert G. Brown
2010-01-07 1:50 ` Gerard Jungman
2010-01-07 3:29 ` Robert G. Brown
[not found] ` <4a00655d1001062110m139c0a8tf2eae7de67da8f6f@mail.gmail.com>
2010-01-07 5:46 ` Rhys Ulerich
2010-01-07 13:22 ` Robert G. Brown
2010-01-08 20:08 ` Gerard Jungman
2010-01-07 18:29 ` Brian Gough [this message]
2010-01-06 12:04 ` Tuomo Keskitalo
2010-01-06 19:57 ` Gerard Jungman
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=87r5q1vkeb.wl%bjg@network-theory.co.uk \
--to=bjg@gnu.org \
--cc=Tuomo.Keskitalo@iki.fi \
--cc=gsl-discuss@sourceware.org \
--cc=jungman@lanl.gov \
/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).