Xref: utzoo comp.lsi:560 sci.electronics:4041
Path: utzoo!attcan!utgpu!water!watmath!clyde!att!osu-cis!tut.cis.ohio-state.edu!husc6!uwvax!umn-d-ub!nic.MR.NET!shamash!nis!ems!pwcs!stag!trb
From: trb@stag.UUCP ( Todd Burkey )
Newsgroups: comp.lsi,sci.electronics
Subject: Re: Edif Example Files-- Part 12 of 23
Keywords: Edif, netlist, schematic, view
Message-ID: <617@stag.UUCP>
Date: 10 Oct 88 03:15:22 GMT
References: <1543@oakhill.UUCP> <6256@pasteur.Berkeley.EDU>
Reply-To: trb@stag.UUCP ( Todd Burkey )
Organization: Mindtools ST Access Group, Plymouth, MN
Lines: 21

In article <6256@pasteur.Berkeley.EDU> spp@zabriskie.UUCP (Steve Pope) writes:
>Talk about clogging the network with garbage.  23 lengthy
>binary postings of EDIF..... gack.  Is there really enough
>interest in this stuff that it can't be put onto tape and
>mailed?

What I find even harder to believe is that an 'EXAMPLE' edif file
should take up so much space! I think of 'example' files as having
just enough information to fully document every type found in the
language. When I wrote an Edif schematic translator several years ago,
I found that I could put every combination of elements, netlists, and
simulation info I needed for a representative sample into less than
400 lines of EDIF. A meg of EDIF language is just too much to deal
with, specially when it isn't even fully verified Edif (as per the
authors original comments). BTW, hasn't anyone come up with a
tokenized version of EDIF yet? A tokenizer would be simple to write
and would reduce most EDIF code that I have seen by an order of
magnitude (if transmission size is an issue).

  -Todd Burkey
   trb@stag.UUCP