On 01/25/2012 02:05 PM, ALEX HUNTLEY wrote:
As whygee pointed out Text I/O is a library issue not a language issue.
Dear Alex,
true, I abbreviated the argument a bit. In C all I/O aspects are handled
by library calls and are thus not part of the language. In Fortran the
opposite approach is used, file and formatted and unformatted I/O are part
of the language. VHDL has a mixed approach, here 'file' is a predefined
type and basic I/O is done by predefined procedures and thus part of the
language, while text I/O for non-predefined types is handled in libraries.
To implement libraries which allow some sort of system interaction beyond
reading/writing text files one must go beyond the confines of VHDL, and
VHPI is the way to go. That was my main point.
>...
I'm not saying that there is never any benefit in using C or Ada or whatever
> language you want in conjunction with VHDL; my point is that this is for
> convenience and avoiding recoding, not because it is essential because of
> language features.
This argument is a bit abbreviated too. Using C is sometimes essential, see
above. On the other hand, complex transaction models are much easier expressed
in SystemC, for example. VHDL is an excellent HDL, but lacks the 'low-level'
interfaces which are accessible via C as well as the ease and conciseness of
for example SystemC for system level modeling.
With best regards, Walter
_______________________________________________
Ghdl-discuss mailing list
[email protected]
https://mail.gna.org/listinfo/ghdl-discuss
