Hello Tristan,
On 07/07/16 18:50, Jonas Baggett wrote:
Hello Tristan,
There is also the case of signals in a package : I would suggest the
following syntax : pkg.the_signal. It seems better to me than
/pkg/the_signal.
Why ? /pkg/the_signal is more regular.
Note you can have two packages with the same name in two different
libraries, so maybe it should be /lib/pkg/the_signal. It is also
possible for an entity to have the name of a library, so maybe it
should be /@lib/pkg/the_signal. At this point we almost follow
the syntax of external path names except '/' is used instead of '.'.
Because it's with this synthax that we access the signal in VHDL. So I
thought that when someone reads lib.pkg.the_signal, it will be clear to
him at first glance that we are accessing a signal inside a package.
Nevertheless, with the /@lib/pkg/the_signal synthax, it's also clear.
Then if you prefer this synthax, it's fine to me too.
Now I have finished to do the file parser and the tree builder. I have
one question : I tried to use the Types package located in src/types.ads
from my package located in src/grt but I get a compile error as the
compiler can't find it because it is at level - 1. Is it possible to
achieve that ?
PS : Good luck for France tonight .
Usually France looses against Germany
Except this time ;).
Cheers,
Jonas
_______________________________________________
Ghdl-discuss mailing list
Ghdl-discuss@gna.org
https://mail.gna.org/listinfo/ghdl-discuss
