1
0
mirror of https://github.com/myhdl/myhdl.git synced 2025-01-24 21:52:56 +08:00

proofread

This commit is contained in:
Jan Decaluwe 2018-04-02 08:58:30 +02:00
parent bb69f9f481
commit 8153a3e630
3 changed files with 7 additions and 15 deletions

View File

@ -618,11 +618,4 @@ following output::
290: TRY to get item
StopSimulation: No more events
.. rubric:: Footnotes
.. [#] The name :func:`always_comb` refers to a construct with similar semantics in
SystemVerilog.
.. [#] It also possible to have a reproducible random output, by explicitly providing a
seed value. See the documentation of the ``random`` module.

View File

@ -159,7 +159,7 @@ The API on a block instance looks as follows:
Converts MyHDL code to a target HDL.
*hdl*:'VHDL' or 'Verilog'. Defaults to Verilog.
*hdl*: 'VHDL' or 'Verilog'. Defaults to Verilog.
Supported keyword arguments:

View File

@ -12,10 +12,9 @@ The `block` decorator
Rationale
---------
For historical reasons, the approach for hierarchy extration in previous
versions of MyHDL suffered from significant issues. This resulted in complex
code, a number of non-intuitive API concepts, and difficulties for future
development.
The historical approach for hierarchy extraction in MyHDL suffers from
significant issues. This results in complex code, a number of non-intuitive
API concepts, and difficulties for future development.
In this release, a new `block` decorator is introduced to address these issues.
@ -27,7 +26,7 @@ For an in-depth discussion, see `mep-114`_.
API
---
.. function:: block()
.. function:: block() :noindex:
The `block` decorator enables a method-based API which is more consistent,
simplifies implementation, and reduces the size of the `myhdl` namespace.
@ -66,7 +65,7 @@ The API on a block instance looks as follows:
Converts MyHDL code to a target HDL.
*hdl*:'VHDL' or 'Verilog'. Defaults to Verilog.
*hdl*: 'VHDL' or 'Verilog'. Defaults to Verilog.
Supported keyword arguments:
@ -96,7 +95,7 @@ In the 0.10 release, the old API still available next to the new API based on
the `block` decorator.
It is likely that the old API will be deprecated in a future release, resulting
in backwards incompatiblity for legacy code. Therefore, users are encouraged to
in backwards incompatibility for legacy code. Therefore, users are encouraged to
start using the new API in their development methodology.