Mail Archives: geda-user/2015/08/02/20:56:32
On 08/02/2015 11:47 AM, John Doty wrote:
>> What is the definition of module in he context of gschem?
Floating entity, with ins and outs defined by strings/characters, related by name to netlist sub-schematics
if more definitions are in place, else not.
On 08/02/2015 12:21 PM, karl AT aspodata DOT se wrote:> Do you have two source attribs in the symbol, or do you have a
> symbol ab.sym in the schematic a.sch, where the symbol have a
> source=b.sch attribute ?
On 08/02/2015 01:52 PM, John Doty wrote:> Two source attribs in the symbol. Like slotdef, you can have as many source attribs as
you need in a symbol. This could be considered a design defect: how do you promote and override this sort of attrib? Maybe these
should be multi-line instead.
This kind of thing really strongly impacts/possibly-destroys hierarchic schematic usefulness.
I don't have any mathematical proofs, but my gut says, "keep a module definition same-as-chip-design-methods,
as a single ins/outs list associated with a graphic symbol or code chunk, and with a mechanism to convert between
'code chunk for the module container' and graphic-symbol at will by an easy to launch program."
- Raw text -