X-Authentication-Warning: delorie.com: mail set sender to geda-user-bounces using -f X-Recipient: geda-user AT delorie DOT com Date: Tue, 15 Sep 2015 22:49:40 +0200 (CEST) From: Roland Lutz To: geda-user AT delorie DOT com Subject: Re: [geda-user] shortest way towards parsing .pcb files outside pcb In-Reply-To: <201509131820.t8DIKUV5028308@envy.delorie.com> Message-ID: References: <201509120239 DOT t8C2dAiO026962 AT envy DOT delorie DOT com> <201509122223 DOT t8CMNhaZ024482 AT envy DOT delorie DOT com> <20150913004237 DOT 6f386c69 AT jive DOT levalinux DOT org> <201509131820 DOT t8DIKUV5028308 AT envy DOT delorie DOT com> User-Agent: Alpine 2.00 (DEB 1167 2008-08-23) MIME-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII; format=flowed 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 On Sun, 13 Sep 2015, DJ Delorie wrote: > at one point we designed a binary representation designed for fast > loading and smaller disk storage. The speedup was much greater than we > expected (it was a large commonly-used file). gEDA files are read - when opening a file - when loading a symbol/footprint from the library - when importing a schematic into PCB - when processing a file with a command-line tool and written - when saving a file - when auto-saving None of these operations are time-critical. The only one of these operations for which I ever experienced significant lag was importing a schematic into PCB, and even then, the time spent loading the schematic files was neglegible (yes, I did perform benchmarks).