Mail Archives: geda-user/2015/08/02/12:47:49
On Aug 2, 2015, at 11:48 AM, Edward Hennessy (ehennes AT sbcglobal DOT net) [via geda-user AT delorie DOT com] <geda-user AT delorie DOT com> wrote:
>
>> On Aug 2, 2015, at 8:01 AM, John Doty <jpd AT noqsi DOT com> wrote:
>>
>> Making gschem more module-oriented is an invitation to confusion.
>
> What is the definition of module in he context of gschem?
When expanding hierarchy, gschem and gnetlist treat the pages listed in the source= attributes of a symbol as a single entity. I’ve called that a module, having no official term. For gschem, the association is loose: basically it opens all of the pages for a module when you go down into the the module from the next level up. Otherwise, gschem treats them as independent pages. For gnetlist, the association is tighter: it treats all of the circuits in a module as if they were drawn on one page.
The top level is similar, except there are no source= attributes driving it. Gschem treats every page at top level independently. Gnetlist treats them as if they are one page.
Note that it is entirely possible to create distinct modules from overlapping sets of schematic pages. You can have an ab.sym with source=a.sch and source=b.sch along with a zb.sym with source=z.sch and source=b.sch.
>
> Ed
>
John Doty Noqsi Aerospace, Ltd.
http://www.noqsi.com/
jpd AT noqsi DOT com
- Raw text -