X-Authentication-Warning: delorie.com: mail set sender to geda-user-bounces using -f X-Recipient: geda-user AT delorie DOT com X-Original-DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=20120113; h=date:from:to:subject:message-id:in-reply-to:references:mime-version :content-type:content-transfer-encoding; bh=tHF5qIkJjRKL32sr3UHsM0x2KMHc8yNHCUJVNfGxUD0=; b=japLem6qTS4U/RZuRwZJkPOODXFkXTlKgIuyAqQMkpDqwsJsCrDlwWX4g0PajN7IKn dcG3BZrYw1roeViFHfehhMv8VBljxrmyGTU5UG10ljEgwWeh0LCTUZWsZEZNCGh/n28A lEp1VrNmQj/iEFiTK5BiLeCminrg0Xlw+VzL2qTR/5mAcBUC84CpVwoJfRos0ZZmrIWo hzRwtAReftWxJugsxRNf/3o5ytrVnFj20FHu8UAQh4BE++wMb3lqMmyPoW1fWWCdaCVI oVJOyUmgzD8tMSv2C2lTXSNUofaKzQpoQApdydtLKUMuahWGZRE5WAjY46vY5/nzK01y D+JA== X-Received: by 10.194.172.2 with SMTP id ay2mr45136265wjc.137.1451062137537; Fri, 25 Dec 2015 08:48:57 -0800 (PST) Date: Fri, 25 Dec 2015 17:48:52 +0100 From: "Nicklas Karlsson (nicklas DOT karlsson17 AT gmail DOT com) [via geda-user AT delorie DOT com]" To: geda-user AT delorie DOT com Subject: Re: [geda-user] A fileformat library Message-Id: <20151225174852.65c59a22bbdfb7d2fb344fb7@gmail.com> In-Reply-To: <201512240626.tBO6QuW0031998@envy.delorie.com> References: <20151222232230 DOT 12633 DOT qmail AT stuge DOT se> <0F6F1D0F-4F07-48EA-90FE-836EAD4E2354 AT noqsi DOT com> <20151223194905 DOT 7676 DOT qmail AT stuge DOT se> <0AB5D926-731F-4A49-AA26-D06DAE7C2CB0 AT noqsi DOT com> <201512240626 DOT tBO6QuW0031998 AT envy DOT delorie DOT com> X-Mailer: Sylpheed 3.5.0beta1 (GTK+ 2.24.25; x86_64-pc-linux-gnu) Mime-Version: 1.0 Content-Type: text/plain; charset=US-ASCII Content-Transfer-Encoding: 7bit Reply-To: geda-user AT delorie DOT com Errors-To: nobody AT delorie DOT com X-Mailing-List: geda-user AT delorie DOT com X-Unsubscribes-To: listserv AT delorie DOT com Precedence: bulk > > I think that having a file format that enables simple means to > > achieve simple (but specialized) ends is essential to a good > > toolkit. > > Any SQL implementation refutes that. Nobody touches the SQL data file > itself, they all go through a SQL interpreter that accesses the data > on their behalf. Specialized ends are implemented on top of this > interpreter. > > Granted, this means we'd need a well-defined way to do pretty much > anything through whatever means we provide, but saying "access to the > file is required" is just plain wrong. "Access to the data" is a more > appropriate requirement, but making the data file tweakable is a weak > solution to that - no controls, no validation, etc. A good start would b e to factor out the specialized ends.