[phdl-devel] a few short comments on Wes' comments.

[peter d. <hd...@ho...>]

Wes, thanks for getting all that down in words. Here are my thoughts on your comments.

>= Packages and Imports =
I question whether we want this type of thing at all.  Right now I think it is optional.  When I write PHDL code I will probably always use this style to fully specify a device where I use it.
iinst oscillator of dev_pack.CB3LV-3I {EOH=open; OUT=clk100; VCC=+3V3; GND=gnd;}

 = Required Attributes =
It sounds right what you are saying about making all attributes optional.  

It sounds like all attributes, including my beloved PINCOUNT, can be optional.  I don't put PINCOUNT on my resistor definitions for example.

Big, fat, all UPPERCASE attributes do seem wrong.  Let's do whatever is right.  I don't know the answer to all these case issues but after 50 years living in the Computer Age we should know what to do.

 == Attributes on Everything ==
Now you are scaring me.  I sounds like you are evolving PHDL toward a generalized connection definition tool instead of something tweaked to just to do PCB's.  Maybe that would be practical.

== Pin Types ==
I agree with Wes on this.  Plus, it simplifies the language to eliminate those keywords from the language.  I will stay tuned to see more on the idea of Attributes on Anything and how that might be used down the road.

== Info Statement ==
I am ok with removing this feature.  I like the idea of processing the design into a report using doxygen. That sounds like something I could figure out. :-)

== Reference Designator Prefix Combining ==
Exactement.

== inst vs subinst ==
I can see a small value to the review of retaining "subinst".  It tips them off in a very concrete way to look for a subdesign and not for a device to check.  Consider this subinst:
subinst supply_1V2 of volt_reg {vin=+5V; vout=+1V2; gnd=gnd;}
It could be a three pin LDO or a complete regulator with decoupling, etc.

I am also glad that we are hammering on the spec now but we should forgive ourselves for not knowing all this up front.  I think having a pretty darn good working PHDL compiler all this time has made it possible to know what we want, which is very close to what we have.  I still believe, more than ever, that typing in board designs is much smarter than clickety-clicking on a silly drafting tool.  

Bonsoir,

  Pete