mirror of
https://github.com/nickmqb/wyre.git
synced 2025-12-15 15:00:26 -08:00
Tweak docs
This commit is contained in:
parent
c52977fa9d
commit
d54160bd40
2 changed files with 2 additions and 2 deletions
|
|
@ -45,7 +45,7 @@ What does Wyre look like? Here is a basic example design with 2 modules, a clock
|
|||
|
||||
A while back I got a Lattice iCE40 FPGA to learn more about how computers work at a low level. I've had a lot of fun making designs for it in Verilog. During the process I kept track of gripes with the toolchain. I ended up with a list of mostly minor things, but nonetheless a list that had a fair amount of items. I felt that there were enough items to justify building some new tooling, and Wyre is the result.
|
||||
|
||||
Compared to Verilog, Wyre aims to cut down on verbosity, improve design iteration speed and reduce errors (via strong typing). Wyre compiles to Verilog, so any design can be fed through an existing Verilog-based toolchain.
|
||||
Compared to Verilog, Wyre aims to cut down on verbosity, reduce errors (via strong typing) and improve design iteration speed. Wyre compiles to Verilog, so any design can be fed through an existing Verilog-based toolchain.
|
||||
|
||||
Some other hardware definition languages try to abstract away the hardware in some ways, with features like memory inference and various generative constructs. These higher level features are explicit non-goals for Wyre. Instead, Wyre aims to stay close to the hardware.
|
||||
|
||||
|
|
|
|||
|
|
@ -6,7 +6,7 @@ Before we begin, a quick note on syntax.
|
|||
|
||||
In Wyre, whitespace before a line (i.e. indentation) is significant. Besides using { and } for blocks, Wyre expects the contents of each block to be indented (like in Python). This is done to improve compile error recovery and compile error message quality.
|
||||
|
||||
In order for this to work, Wyre needs to know your tab size. You must specify your tab size via the compiler command line argument `--indent [n]`.
|
||||
In order for this to work, Wyre needs to know your tab size. You must specify your tab size via the compiler command line flag `--indent [n]`.
|
||||
|
||||
If you don't want to use significant whitespace, simply pass `--indent 0` (but be warned that you might get lower quality compile error messages!).
|
||||
|
||||
|
|
|
|||
Loading…
Add table
Add a link
Reference in a new issue