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=LuV6/9ffJY+vXgCsnLgsOIXw8qHh1MzGWN0N5Djiri4=;
	b=X3WmutppU4PG3bG4D9Gjfwbw3KGKHBSFqivHAmK6oFETaffs9ENk+HxwBd384ppuvY
	fnwosz3VCU7dWeUhYVQgQVnCeWoo6QtzoaiPIcr3+P6r8rnsv3zhha6YyNvwcqh16bKn
	6aINXTLWkveLpWwpExELK7nZ7dqE/bJv2nr5F9WSGG2IBqPyFPuQc+3jNvWzfZkcURWR
	L/HlT0v3FQC3VlL3o81uXOouTfP5D60X8N8cQzQ0oymSgt4kaDNV3hAaNkZEc+Kgm/ZE
	q5DEZiMFMc3lDFQwDEwe4Urv6dh8PiQ44QLnDBXumsqOJ/fwfenIc0CwAMJC1oddwHLA
	X8UA==
X-Received:	by 10.194.161.166 with SMTP id xt6mr11932068wjb.98.1451254739765;
	Sun, 27 Dec 2015 14:18:59 -0800 (PST)
Date:	Sun, 27 Dec 2015 23:18:58 +0100
From:	"Nicklas Karlsson (nicklas DOT karlsson17 AT gmail DOT com) [via geda-user AT delorie DOT com]" <geda-user AT delorie DOT com>
To:	geda-user AT delorie DOT com
Subject:	Re: [geda-user] A fileformat library
Message-Id:	<20151227231858.6ecd296e38fcf6b1ff7da31b@gmail.com>
In-Reply-To:	<CAC4O8c-zt8B=joDd+ws77D2jt6aZf3MWfR_dAvpzGcNuBrTURQ@mail.gmail.com>
References:	<1512221837 DOT AA25291 AT ivan DOT Harhan DOT ORG>
	<CAJXU7q_mXmipJ1fLvLpuLvnYjktV2SHoA+bG=L5+E-EfdygeOA AT mail DOT gmail DOT com>
	<s6n37uumanm DOT fsf AT blaulicht DOT dmz DOT brux>
	<CAJXU7q_qxdvJaejF-VcY=u7VHZ-zrfrc+Z7-qSwfFyPdy-umxw AT mail DOT gmail DOT com>
	<B02363CD-469D-493A-AC15-1D5DC7836982 AT noqsi DOT com>
	<20151222232230 DOT 12633 DOT qmail AT stuge DOT se>
	<0F6F1D0F-4F07-48EA-90FE-836EAD4E2354 AT noqsi DOT com>
	<CAM2RGhTficnys3a4xs=UBFvk8aPwpzYWUADFLP_pUQ+R1iKs0g AT mail DOT gmail DOT com>
	<0FCF3774-F93C-4BFF-BB61-636F75DCCACB AT noqsi DOT com>
	<CAC4O8c_UAiFE-vGfoE2tXppHLhaa0dSYz9o_rkdCBo7_SRRtxw AT mail DOT gmail DOT com>
	<FFBE7623-E240-4798-96B0-2BECF56C8E29 AT noqsi DOT com>
	<CAC4O8c980g1gj15=5njstC_BT-WYDgKQx9BRycdFKA8OvgtiOg AT mail DOT gmail DOT com>
	<B54C0E1F-1986-4C79-9F70-7F1919B8B26D AT noqsi DOT com>
	<CAC4O8c9bxJP1eMG4yz3YwKkQJRmsDGmLQ0aMd5pJRyu0WpdCtQ AT mail DOT gmail DOT com>
	<C1CFCCEE-C64A-4E49-AA64-446C061656D6 AT noqsi DOT com>
	<CAC4O8c-zt8B=joDd+ws77D2jt6aZf3MWfR_dAvpzGcNuBrTURQ AT mail DOT gmail DOT com>
X-Mailer:	Sylpheed 3.5.0beta1 (GTK+ 2.24.25; x86_64-pc-linux-gnu)
Mime-Version:	1.0
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

> > Depends on what language you’re using. It will be different for different
> > APIs. Is it more convenient to encode x,y as some sort of pair, or
> > separate? Or are you being LISPy and going for positions within lists
> > anyway with cadadr et al.?
> >
> 
> No, I meant that the data file itself will tend to have named fields,
> rather than arrays with unnamed heterogeneous elements like the current
> format
> For the agile languages the names will turn into hashes/dicts/whatever when
> vivified.

gschem files in sort of use named fields. Named fields use more resources to handle but accessing data on disk is done rather seldom and some delay is even expected so in this case efficiency of accessing data is less important.

Once read from disk it may however be useful to transform to something more efficient. Then drawing objects on screen it is for example very useful with a efficient view of the data for this purpose maybe in the form of a cache.

Then checking for clearance it may be useful to store the objects on copper layers in suitable data structures for this purpose, at least if there are many combinations to check.

- Raw text -