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
Hi all,
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 guess noone would object.
I'm kind of an impatient software guy, so I've been looking
As whygee pointed out Text I/O is a library issue not a language issue.
Your example of using an already-written piece of code was precisely where
I said multi-language simulation could be useful.
However the main point is that when you compare the languages both have the
concept of functions /
I would disagree that integration with C is essential - far from it.
I've never found any reason to write test-benches in C rather than VHDL.
VHDL has all the features of C plus, has inherently a concept of
parallelism and inherently a concept of time.
The only real reason to interface with C
Hi Walter !
On Wed, 25 Jan 2012 00:01:08 +0100, Walter F.J. Mueller wrote:
Dear Alex,
first I disagree with your statement VHDL has all the features of
C.
Apart from reading and writing sequential text files the I/O features
of VHDL, at least the portable ones, are very limited.
Correction
On Jan 14, 2012, at 11:09 PM, Walter F.J. Mueller wrote:
I put it a little wider:
- when ghdl wants to survive on the long run it has to implement
also the major vhdl-2008 language features in the future.
- by the time vhdl-2008 is supported by synthesis tools one wants
to use some of
Hi,
it is nice to think about all kinds of implementation alternatives.
In all this keep in mind that integration with C language programs
is essential for the implementation any sort of test bench. I used
the VHPIDIRECT mechanism in ghdl for this to interface to plain C
code, and this is at the
