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=n08BCX4/z60poB2/RdUPjZdS6IxDtRH1dKrtCld67uY=; b=SS1ZQVJH36Z8aXH1zjIo+fseUWC7OFmn3E9u30FhAPnKMKBNNAsmaFT8ZbSmUgil5S J88VHmjTKsPgG5MDTuuBliMe7jqKSPKU1c0m64L6531va8i8GxYVUjTasw/M4l5RSHKh 7Dl6EBTiw/sfQDmHBp1dmcoQHf4ZvbIj48BAD0lgScb+PkIYXLq6cPLycdybdTxT03nv RGWq2AEA87ajHzEJGv+FEJ9xuhLWXcCcHZW2gRGwjVhJeN3HNLBdohCJn3ELHm9NKfYp xLa/rdW0Pw1leqt10WdStOY1pk8TlwynZa6YdZbQ/zAfC2EfP7Zx3iHHXvgUrdYOqRxI uxAA== X-Received: by 10.28.126.84 with SMTP id z81mr9026695wmc.29.1452070432956; Wed, 06 Jan 2016 00:53:52 -0800 (PST) Date: Wed, 6 Jan 2016 09:53:51 +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: <20160106095351.410e3f2407176052d835251e@gmail.com> In-Reply-To: References: <1512221837 DOT AA25291 AT ivan DOT Harhan DOT ORG> <0FCF3774-F93C-4BFF-BB61-636F75DCCACB AT noqsi DOT com> <20160105182120 DOT 3237F809D79B AT turkos DOT aspodata DOT se> <8E0210CD-0694-4717-A7B1-3224E39691DA AT sbcglobal DOT net> 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 recently did a tiny bit of work on the parser in pcb. Of course we > should continue to support it, but it's going to be tough to extend it > much. It's already overloaded in weird ways (e.g. thermals are parsed as > flags, with their own non-flex sub-syntax, even though they don't set any > actual flags). If you do extend it you do hard work and still only pcb can > read it. Of course you still have to teach the innards of pcb about your > extensions in order for them to do anything useful. A good start might be to write down what need to be stored even though they are not implemented right now and maybe never will be: 1. Padstack, probably as collection of ordinary drawing primitives. 2. Local copy and reference so update is possible. 3. Net and possible segment attribute for route style, width. 4. Net clerances between any net. 5. Net clerance classes although (4.) could be extended before entering pcb. 6. Trace impedance. 7. Differential impedance? 8. Pin swapping! 9. Slot swapping. > ... Speaking for myself, I > prefer softwares to spit out a big fat FAIL message and quit, than to > silently try to work when they cannot guarantee correct operation. Indeed it is, I tried visual basic or is it this they call C# and it just continue. Nicklas Karlsson