From mboxrd@z Thu Jan 1 00:00:00 1970 X-Spam-Checker-Version: SpamAssassin 3.4.4 (2020-01-24) on polar.synack.me X-Spam-Level: X-Spam-Status: No, score=-1.3 required=5.0 tests=BAYES_00,INVALID_MSGID autolearn=no autolearn_force=no version=3.4.4 X-Google-Language: ENGLISH,ASCII-7-bit X-Google-Thread: 103376,71aa8acfc8368f1c X-Google-Attributes: gid103376,public From: Gautier Subject: Re: BLAS Date: 2000/05/12 Message-ID: <391C3A57.CD9F6372@maths.unine.ch>#1/1 X-Deja-AN: 622624670 Content-Transfer-Encoding: 7bit References: X-Accept-Language: en Content-Type: text/plain; charset=us-ascii X-Trace: 12 May 2000 19:07:37 +0100, mac13-32.unine.ch Organization: Maths - Uni =?iso-8859-1?Q?Neuch=E2tel?= MIME-Version: 1.0 Newsgroups: comp.lang.ada Date: 2000-05-12T00:00:00+00:00 List-Id: Duncan: > By the way, I'm in two minds as to whether the Matrix and Vector types > should be defined in the package No please! > or passed as generic parameters. YES! (IMHO) Why? With a generic finite element kernel, a generic sparse matrix package, a generic band matrix package, and others like bandwidth reductors and so on the proliferation of different types for similar things on the same program becomes completely infernal. BUT... there might be good reasons _for_ defining it in the BLAS package: e.g., because BLAS is at the lowest-level. Anyway defining in the package reduces freedom. Other opinions ? (for Float_Type'Base & Co: no clue) _____________________________________________ Gautier -- http://members.xoom.com/gdemont/