Mail Archives: geda-user/2015/07/10/12:12:45
On Fri, 10 Jul 2015, Vladimir Zhbanov (vzhbanov AT gmail DOT com) [via geda-user AT delorie DOT com] wrote:
> On Fri, Jul 10, 2015 at 03:49:27PM +0200, gedau AT igor2 DOT repo DOT hu wrote:
>>
>>
>> On Fri, 10 Jul 2015, Vladimir Zhbanov (vzhbanov AT gmail DOT com) [via geda-user AT delorie DOT com] wrote:
>>>
>>> TL;DR
>>> Have you ever tried to read 'info geda-scheme'?
>>
>> No.
>>
>> But I do div down in random unknown code written in random unknown-to-me
>> languages from time to time to fix something or make small modifications, so
>> I know when it takes much longer than it should. With scheme, it does.
>>
>> I did it once, it enables me to access most of the data I need, so I won't
>> need to do it ever again.
>>
>> Regards,
>>
>> Igor2
>
> If your task was outputting coords of line segments in your schematic,
> it is as easy as the script attached. With little modifications you can
> output it to any file. You can use it in gschem or with the gaf utility
> if you want to make it a stand-alone program.
Thanx.
>
> And for the record: gnetlist is g-netlist. It's for netlisting (for work
> with pin, nets, components) rather than accessing any schematic objects.
>
> My wish to all participants of these thread (hope it's non-offensive):
> please, try to be less ignorant, better ask here rather than flood the
> list with your private opinions on how everything around is bad.
Btw, it was you who TL;DR'd. One part of my story was right about trying
to extract attributes and netlist stuff with gnetlist That was the
part that took incredibly long due to scheme. In turn this experience made
me not even consider using it again for the other task which was coord
extraction.
So next time I have something similar to solve, I will first ask you for
the scheme code and only if that fails I do the dirty sch-parsing awk
fewliner.
Regards,
Igor2
- Raw text -