X-Authentication-Warning: delorie.com: mail set sender to geda-user-bounces using -f
X-Recipient: geda-user AT delorie DOT com
X-Virus-Status: Clean
X-Virus-Scanned: clamav-milter 0.98.4 at av02.lsn.net
Message-ID: <54DBCB51.2080000@ecosensory.com>
Date: Wed, 11 Feb 2015 15:36:17 -0600
From: John Griessen <john AT ecosensory DOT com>
User-Agent: Mozilla/5.0 (X11; Linux x86_64; rv:31.0) Gecko/20100101 Icedove/31.4.0
MIME-Version: 1.0
To: geda-user AT delorie DOT com
Subject: Re: [geda-user] Using Lua to safely read configuration and layout
 files (program attached)
References: <CAOFvGD7WSM+qErYxvhe2m9YxwpAUvcEGsxgtYTZZmE_+v3Tpig AT mail DOT gmail DOT com>
In-Reply-To: <CAOFvGD7WSM+qErYxvhe2m9YxwpAUvcEGsxgtYTZZmE_+v3Tpig@mail.gmail.com>
Content-Type: text/plain; charset=utf-8; format=flowed
Content-Transfer-Encoding: 7bit
Reply-To: geda-user AT delorie DOT com

On 02/10/2015 02:28 PM, Jason White wrote:
> Levente, I just [yesterday] tried a script with over 200,000 entries
> (roughly 9.8
> megabytes of text) and I am happy to report it worked without error.
>
> Here is a link to the file I used
> https://drive.google.com/file/d/0BwP0qhqyaTIIYVlISkQwMXJtRlU/view?usp=sharing

What was the time like on an ordinary computer with just two cores and no special parallelizing
help?  Are there enough benefits to using JSON to offset the larger file size?
I like that it could tame white space differences when stored in version control.

How would that work?  How does JSON decrease the impact of white space differences
when stored in version control?

On 02/08/2015 05:47 AM, Christian Riggenbach wrote:> If you use an versioning system for the schematics today, you get a mess of
 > chopped "gibberish" now, as the normal line based patches are not human
 > readable.

Would making code commits always based on content between { and } help that?