Fixed minor rst error + lowercase 'hy' occurance
- (Seemingly) accidental placement of a character meant that the backticks weren't picked up and displayed nicely. - Everywhere you refer to 'Hy', it has a capital 'h'. Here it did not. Fixed up minor grammar issue in one sentence Fixed minor inconsistency with Python and Hy code - Added variable assignment before code example
This commit is contained in:
parent
042bc973b3
commit
fe4f677ed2
@ -168,7 +168,7 @@ There are some advantages to having a code structure that's actually a
|
||||
very simple data structure as the core of Lisp is based on. For one
|
||||
thing, it means that your programs are easy to parse and that the
|
||||
entire actual structure of the program is very clearly exposed to you.
|
||||
(There's an extra step in hy where the structure you see is converted
|
||||
(There's an extra step in Hy where the structure you see is converted
|
||||
to Python's own representations ... in "purer" Lisps such as Common
|
||||
Lisp or Emacs Lisp, the data structure you see in the code and the
|
||||
data structure that is executed is much more literally close.)
|
||||
@ -258,6 +258,7 @@ In Hy, you would do:
|
||||
|
||||
.. code-block:: clj
|
||||
|
||||
(setv somevar 33)
|
||||
(cond
|
||||
[(> somevar 50)
|
||||
(print "That variable is too big!")]
|
||||
@ -570,7 +571,7 @@ language on top of that. Many features of Hy are macros, like ``when``,
|
||||
To use macros defined in a different module, it is not enough to
|
||||
``import`` the module, because importing happens at run-time, while we
|
||||
would need macros at compile-time. Instead of importing the module
|
||||
with macros, it must be ``require``d:
|
||||
with macros, ``require`` must be used:
|
||||
|
||||
.. code-block:: clj
|
||||
|
||||
|
Loading…
x
Reference in New Issue
Block a user