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

Fixed two typos, added an intbv class link and reformated an paragraph

Browse Source
This commit is contained in:
Guenter Dannoritzer 2009-01-09 18:07:35 +01:00
parent 63b8f09a70
commit ac26dda8a5
1 changed files with 6 additions and 7 deletions
Show Stats Download Patch File Download Diff File Expand all files Collapse all files

13
doc/source/manual/intro.rst
View File

@ -380,8 +380,8 @@ The following example shows how to do that::
>>> a = intbv(24)[5:] >>> a = intbv(24)[5:]
What actually happens here is that first an unconstrained :class:`intbv` What actually happens here is that first an unconstrained :class:`intbv`
is created, which is then sliced. Slicing an intbv returns a new is created, which is then sliced. Slicing an :class:`intbv` returns a new
:class:`intbv` with the constraints set up apppropriately. :class:`intbv` with the constraints set up appropriately.
Inspecting the object now shows:: Inspecting the object now shows::
>>> a.min >>> a.min
@ -615,7 +615,7 @@ They provide low-level types like ``signed`` and ``unsigned`` for
arithmetic. The rules for arithmetic with such types are much more arithmetic. The rules for arithmetic with such types are much more
complicated than with plain integers. complicated than with plain integers.
In some cases it can be useful to interprete :class:`intbv` objects In some cases it can be useful to interpret :class:`intbv` objects
in terms of "signed" and "unsigned". Basically, it depends on attribute *min*. in terms of "signed" and "unsigned". Basically, it depends on attribute *min*.
if *min* < 0, then the object is "signed", otherwise it is "unsigned". if *min* < 0, then the object is "signed", otherwise it is "unsigned".
In particular, the bit width of a "signed" object will account for In particular, the bit width of a "signed" object will account for
@ -624,10 +624,9 @@ be redundant. From earlier sections, we have learned that the
return value from a slicing operation is always "unsigned". return value from a slicing operation is always "unsigned".
In some applications, it is desirable to convert an "unsigned" In some applications, it is desirable to convert an "unsigned"
:class:`intbv` to a "signed", in other words, to interprete the msb :class:`intbv` to a "signed", in other words, to interpret the msb bit
bit as a sign bit. as a sign bit. The msb bit is the highest order bit within the object's
The msb bit is the highest order bit within the object's bit width. bit width. For this purpose, :class:`intbv` provides the
For this purpose, :class:`intbv` provides the
:meth:`intbv.signed` method. For example:: :meth:`intbv.signed` method. For example::
>>> a = intbv(12, min=0, max=16) >>> a = intbv(12, min=0, max=16)