X-Authentication-Warning: delorie.com: mail set sender to geda-user-bounces using -f X-Recipient: geda-user AT delorie DOT com X-Proofpoint-Virus-Version: vendor=fsecure engine=2.50.10432:5.13.68,1.0.33,0.0.0000 definitions=2015-02-08_03:2015-02-08,2015-02-08,1970-01-01 signatures=0 X-Proofpoint-Spam-Details: rule=notspam policy=default score=0 spamscore=0 suspectscore=3 phishscore=0 adultscore=0 bulkscore=0 classifier=spam adjust=0 reason=mlx scancount=1 engine=7.0.1-1412110000 definitions=main-1502080180 Sun-Java-System-SMTP-Warning: Lines longer than SMTP allows found and wrapped. From: Chris Smith Content-type: text/plain; charset=utf-8 MIME-version: 1.0 (1.0) Subject: Re: [geda-user] FOSDEM Message-id: Date: Sun, 08 Feb 2015 16:32:35 +0000 References: <1420499386 DOT 3521 DOT 3 DOT camel AT cam DOT ac DOT uk> <20150202152654 DOT GA13336 AT cuci DOT nl> <54CFD589 DOT 9040702 AT xs4all DOT nl> <20150203112631 DOT 3507a0c1 AT Parasomnia DOT thuis DOT lan> <20150204054256 DOT Horde DOT Pm1JV8RJbICk9SHvIGwZ7A3 AT webmail DOT in-berlin DOT de> <20150204193720 DOT Horde DOT 42xUN-NzhCJRWZne-M5eCQ1 AT webmail DOT in-berlin DOT de> <90236728-E79D-47C7-BFB1-34140DB85ACB AT sbcglobal DOT net> <201502042333 DOT t14NX28o024789 AT envy DOT delorie DOT com> <7C1A5871-3056-482C-BC58-173D90D80F77 AT icloud DOT com> <38B551E5-A593-4B72-9156-823A8B4B31F1 AT noqsi DOT com> <5583C086-E36C-4E79-BB7A-CCCCCDEE5686 AT icloud DOT com> In-reply-to: To: "geda-user AT delorie DOT com" X-Mailer: iPad Mail (12B466) Content-Transfer-Encoding: 8bit X-MIME-Autoconverted: from quoted-printable to 8bit by delorie.com id t18GWepb012992 Reply-To: geda-user AT delorie DOT com > On 8 Feb 2015, at 15:30, John Doty wrote: > > Shudder. Here anybody who’s processing this in a textutilish way needs to write a whole bunch of extra stuff to remove all of the unneeded punctuation. “5” is a perfectly good number, but “5,” isn’t. Ok, make it "5 ," then. Lua doesn't care about the white space and neither do I. > This also demonstrates the sort of misconception that can creep in with this approach. “device=‘resistor’” is wrong: to the parser, text is text. Whether the “=“ is to be interpreted depends on what you are doing. In text sometimes there’s no “=“, sometimes more than one. Often, “=" punctuates an attribute, but sometimes it’s just part of a note to the reader. Not the parser’s call. I just showed one way of representing it. 'device=resistor' is just as acceptable as device='resistor'. > The file format should be language-neutral. We have that now. No we don't. We have a format that's clearly biased towards your toolset. > If it ain’t broke, don’t fix it. If Lua is as good as you claim, you could have written a parser for the existing format in the time we’ve wasted here. What problem does changing the file format solve? It brings consistency and structure. It means we have one single format and language that can be used across the entire gEDA suite, for data, configuration and scripting; and it becomes trivial to manipulate that data in a well ordered manner - gnetlist becomes a rather trivial wrapper that simply loads the data file and chooses the correct backend. The backend has immediate, unfettered access to the entire object tree without any information hiding or abstraction. That's what you wanted, wasn't it? Frankly, if we're reduced to quibbling about comma and quote placement then I'm inclined to believe that you're just arguing for the sake of it; that you're happy to stand against any form of progress if it has any impact at all on the way you currently work. That being the case I'm happy simply to modify your initial command to: convert_to_johns_friendly_format.lua Interface.*.sch | awk '/^C /{print $7}' | sort | uniq and just jog on. Chris