On Fri, 27 Jun 2008 06:34:39 -0700 (PDT), koyel.aphy@[EMAIL PROTECTED]
wrote:
>This is what I am using right now and I get the errors
>
>Error at 30.000 ns(1): Textio read:: called on empty string or line
>at 30.000 ns(1): Error: Oops, bad separator
>this continues upto 100 ns.
Is it time for me to get angry? Surely not.
ADD SOME DIAGNOSTICS.
There is a CLUE here...
Textio read:: called on empty string or line
Now, I can't even start to guess why this might be so.
But if I were trying to debug it, I would begin by
printing each line of text that I read from the file,
before I start doing the read() operations. Something
like this would do the job:
...
readline(F, L); -- get line of text
-- Let's have a look at that line, before we read it
re****t "Got line from file: '" & L.all & "'";
...
And we'll probably find that there's a blank line, or
some spurious separator character, or something of the sort,
that's preventing our simple-minded read() operation from
working. And then we can fix it. This is a technique
that we skilled engineers have come to know as "debugging".
Alternatively, of course, we could continue to pester
a newsgroup with incomplete error re****ts.
Choose which you think is likely to be more productive
and a better learning experience.
--
Jonathan Bromley, Consultant
DOULOS - Developing Design Know-how
VHDL * Verilog * SystemC * e * Perl * Tcl/Tk * Project Services
Doulos Ltd., 22 Market Place, Ringwood, BH24 1AW, UK
jonathan.bromley@[EMAIL PROTECTED]
contents of this message may contain personal views which
are not the views of Doulos Ltd., unless specifically stated.
|
