From: James Bergstra <bergstrj@iro.umontreal.ca>
To: Gerard Jungman <jungman@cybermesa.com>
Cc: gsl-discuss@sourceware.org
Subject: Re: containers tentative design summary
Date: Mon, 05 Oct 2009 14:50:00 -0000 [thread overview]
Message-ID: <7f1eaee30910050750l738876b1p41e6bd8ae5aa6d16@mail.gmail.com> (raw)
In-Reply-To: <1254708349.18519.4.camel@ForbiddenPlanet>
Two comments:
I'm a bit rusty with my C structs... but you would need two distinct
static classes to have const and non-const data pointers for your view
right?
Also, it sounds like writing code that will work for a tensor of any
rank (e.g. add two tensors together) might be either tedious or
impossible. I recognize that part of the problem is the lack of
templating and polymorphism, but it would at least be comforting to
see just how bad the situation is via a use case or two in the design
documentation. I (naively?) fear that to get good performance will
require a whole library of functions for even the most basic of
operations.
gsl_marray_add_1_0( gsl_marray_1, double );
gsl_marray_add_1_1( gsl_marray_1, gsl_marray_1);
gsl_marray_add_1_2( gsl_marray_1, gsl_marray_2);
gsl_marray_add_2_2(... )
...
gsl_marray_sub_1_0( ... )
Maybe a system of macros could be designed to help here, but it sounds
like it will never be as easy as writing a couple of for-loops.
James
On Sun, Oct 4, 2009 at 10:05 PM, Gerard Jungman <jungman@cybermesa.com> wrote:
> A summary of the tentative design for containers. Code will follow,
> as soon as a few things are sorted out. (See previous post on
> questions about block/vector/matrix).
>
> --
> G. Jungman
>
>
--
http://www-etud.iro.umontreal.ca/~bergstrj
next prev parent reply other threads:[~2009-10-05 14:50 UTC|newest]
Thread overview: 30+ messages / expand[flat|nested] mbox.gz Atom feed top
2009-10-05 10:12 Gerard Jungman
2009-10-05 14:50 ` James Bergstra [this message]
2009-10-05 23:00 ` Gerard Jungman
2009-10-05 23:45 ` James Bergstra
2009-10-06 19:59 ` Gerard Jungman
[not found] ` <645d17210910060537s762d6323pfd2bec8590ad28e9@mail.gmail.com>
2009-10-06 20:02 ` Gerard Jungman
2009-10-23 21:28 ` Brian Gough
2009-10-27 23:06 ` Gerard Jungman
[not found] ` <7f1eaee30910271628h70785125m68e47c7a7b5c25b7@mail.gmail.com>
2009-10-27 23:49 ` Gerard Jungman
2009-10-29 18:06 ` Brian Gough
2009-10-29 20:41 ` Gerard Jungman
2009-10-29 21:40 ` James Bergstra
2009-10-30 16:54 ` Brian Gough
2009-10-30 16:54 ` Brian Gough
2009-10-05 23:04 ` some general questions Gerard Jungman
2009-10-06 16:21 ` Brian Gough
2009-10-06 20:32 ` Gerard Jungman
2009-10-10 14:45 ` Tuomo Keskitalo
2009-10-24 11:16 ` Brian Gough
2009-10-14 20:00 ` Brian Gough
2009-10-15 18:39 ` Tuomo Keskitalo
2009-11-03 19:44 containers tentative design summary Gerard Jungman
2009-11-09 20:41 ` Brian Gough
2009-11-09 23:06 ` Gerard Jungman
2009-11-14 15:25 ` Brian Gough
2009-11-15 9:13 ` Tuomo Keskitalo
2009-11-15 16:44 ` Jonathan Underwood
2009-11-15 18:41 ` Robert G. Brown
2009-11-16 11:56 ` Brian Gough
2009-11-20 9:37 Justin Lenzo
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=7f1eaee30910050750l738876b1p41e6bd8ae5aa6d16@mail.gmail.com \
--to=bergstrj@iro.umontreal.ca \
--cc=gsl-discuss@sourceware.org \
--cc=jungman@cybermesa.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).