FPGA/myhdl
1
0
Fork 0
mirror of https://github.com/myhdl/myhdl.git synced 2025-01-24 21:52:56 +08:00
Code Issues Projects Releases Wiki Activity

Proof read

Browse Source
This commit is contained in:
jand 2003-03-07 11:06:24 +00:00
parent 6c56dd721d
commit 3f4e93c19a
2 changed files with 5 additions and 6 deletions
Show Stats Download Patch File Download Diff File Expand all files Collapse all files

1
doc/modeling.tex
View File

@ -274,7 +274,6 @@ def fifo(dout, din, re, we, empty, full, clk, maxFilling=sys.maxint):
empty -- empty indication flag
full -- full indication flag
clk -- clock input
Optional parameter:
maxFilling -- maximum fifo filling, "infinite" by default

10
doc/unittest.tex
View File

@ -252,10 +252,7 @@ FAIL: Check that all codewords occur exactly once
Traceback (most recent call last):
File "test_gray.py", line 109, in testUniqueCodeWords
sim.run(quiet=1)
File "/home/jand/project/myhdl/myhdl/Simulation.py", line 87, in run
clauses, clone = waiter.next()
File "/home/jand/project/myhdl/myhdl/Simulation.py", line 161, in next
clause = self.generator.next()
...
File "test_gray.py", line 104, in test
self.assertEqual(actual, expected)
File "/usr/local/lib/python2.2/unittest.py", line 286, in failUnlessEqual
@ -293,7 +290,7 @@ OK
In the previous section, we concentrated on the general requirements
of a Gray code. It is possible to specify these without specifying the
actual code. It is easy to see that there are several codes
that satisfy these requirements. In good XP style, we only tested for
that satisfy these requirements. In good XP style, we only tested
the requirements and nothing more.
It may be that more control is needed. For example, the requirement
@ -382,6 +379,9 @@ Check that the code is an original Gray code ... ok
----------------------------------------------------------------------
Ran 1 tests in 3.091s
OK
\end{verbatim}