From mboxrd@z Thu Jan 1 00:00:00 1970 Return-Path: Received: (qmail 15586 invoked by alias); 15 Nov 2009 18:41:54 -0000 Received: (qmail 15571 invoked by uid 22791); 15 Nov 2009 18:41:52 -0000 X-SWARE-Spam-Status: No, hits=-3.6 required=5.0 tests=BAYES_00,RCVD_IN_DNSWL_LOW X-Spam-Check-By: sourceware.org Received: from mail.phy.duke.edu (HELO mail.phy.duke.edu) (152.3.182.2) by sourceware.org (qpsmtpd/0.43rc1) with ESMTP; Sun, 15 Nov 2009 18:41:00 +0000 Received: from localhost (localhost [127.0.0.1]) by mail.phy.duke.edu (Postfix) with ESMTP id 9091A780B7; Sun, 15 Nov 2009 13:40:57 -0500 (EST) Received: from mail.phy.duke.edu ([127.0.0.1]) by localhost (mail.phy.duke.edu [127.0.0.1]) (amavisd-new, port 10026) with LMTP id av1Rwth+Bcgi; Sun, 15 Nov 2009 13:40:57 -0500 (EST) Received: from lilith.rgb.private.net (cpe-069-134-079-008.nc.res.rr.com [69.134.79.8]) by mail.phy.duke.edu (Postfix) with ESMTP id 6C1007807F; Sun, 15 Nov 2009 13:40:57 -0500 (EST) Date: Sun, 15 Nov 2009 18:41:00 -0000 From: "Robert G. Brown" To: Jonathan Underwood cc: gsl-discuss@sourceware.org Subject: Re: containers tentative design summary In-Reply-To: <645d17210911150843h7034c341yb453d3fb3f3fb8cf@mail.gmail.com> Message-ID: References: <1257277549.19313.118.camel@manticore.lanl.gov> <1257808063.11663.3.camel@manticore.lanl.gov> <87tywxtbf4.wl%bjg@network-theory.co.uk> <4AFFC617.9050707@iki.fi> <645d17210911150843h7034c341yb453d3fb3f3fb8cf@mail.gmail.com> User-Agent: Alpine 2.00 (LFD 1167 2008-08-23) MIME-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII; format=flowed Mailing-List: contact gsl-discuss-help@sourceware.org; run by ezmlm Precedence: bulk List-Id: List-Subscribe: List-Archive: List-Post: List-Help: , Sender: gsl-discuss-owner@sourceware.org X-SW-Source: 2009-q4/txt/msg00044.txt.bz2 On Sun, 15 Nov 2009, Jonathan Underwood wrote: > I think it would be better if GSL, being written in C, were to > present the most functional interface at the expense of sacrificing > type safety, and higher level language bindings could then wrap that > API and do type checking as needed. As gerard says, C isn't about type > safety. I agree. A good C programmer is comfortable with casts and knows perfectly well that it is up to them to track them. And the compiler (give a chance) will usually at least warn you about apparent inconsistency. rgb > > Jonathan > Robert G. Brown http://www.phy.duke.edu/~rgb/ Duke University Dept. of Physics, Box 90305 Durham, N.C. 27708-0305 Phone: 1-919-660-2567 Fax: 919-660-2525 email:rgb@phy.duke.edu