Mirror/wren
1
0
Fork 1
mirror of https://github.com/wren-lang/wren.git synced 2026-01-11 14:18:42 +01:00
Code Issues Packages Projects Releases Wiki Activity

Tweak module docs a bit.

Browse Source
This commit is contained in:
Bob Nystrom
2015-11-09 07:42:48 -08:00
parent 902289d7dd
commit de7b062a03
3 changed files with 22 additions and 22 deletions
Download Patch File Download Diff File Expand all files Collapse all files

18
doc/site/modules/index.markdown
View File

@ -1,15 +1,15 @@
^title Modules
Because Wren can be used both as an embedded scripting language, and as a
full-featured general purpose programming language run from the command line,
the definition of a "built-in" module is a little more complicated than other
languages. They are organized into three categories:
general purpose programming language run from the command line, the definition
of a "built-in" module is a little complicated. They are organized into three
categories:
## Core
There is one core module. It is built directly into the VM and is implicitly
imported by every other module. It contains the classes for the kinds of objects
built directly into the language itself: [numbers][], [strings][], etc.
imported by every other module. It contains the classes for the objects built
directly into the language itself: [numbers][], [strings][], etc.
[numbers]: core/num.html
[strings]: core/string.html
@ -25,9 +25,9 @@ embed Wren in your own host application, you can also include them too. They are
written in Wren and C, but have no external dependencies, so including them in
your application doesn't force you to bring in any other third-party code.
At the same time, they aren't needed by the VM to function, so you can disable
some or all of them if you want to keep your app as small and constrained as
possible.
At the same time, they aren't *needed* by the VM itself to function, so you can
disable some or all of them if you want to keep your app as small and
constrained as possible.
There are a couple of optional modules:
@ -38,7 +38,7 @@ There are a couple of optional modules:
The CLI modules are only available in the standalone command-line Wren
interpreter. They are deeply tied to [libuv][], each other, and other internals
of the command-line app, so can't be easily separated out and pulled into host
of the command-line app, so can't be separated out and pulled into host
applications that want to embed Wren.
[libuv]: http://libuv.org

24
doc/site/modules/template.html
View File

@ -23,22 +23,22 @@
<section>
<h2>core</h2>
<ul>
<li><a href="core">Core</a></li>
<li><a href="core">core</a></li>
</ul>
</section>
<section>
<h2>optional</h2>
<ul>
<li><a href="meta">Meta</a></li>
<li><a href="random">Random</a></li>
<li><a href="meta">meta</a></li>
<li><a href="random">random</a></li>
</ul>
</section>
<section>
<h2>cli</h2>
<ul>
<li><a href="io">IO</a></li>
<li><a href="scheduler">Scheduler</a></li>
<li><a href="timer">Timer</a></li>
<li><a href="io">io</a></li>
<li><a href="scheduler">scheduler</a></li>
<li><a href="timer">timer</a></li>
</ul>
</section>
</nav>
@ -52,20 +52,20 @@
<tr>
<td>
<ul>
<li><a href="core">Core</a></li>
<li><a href="core">core</a></li>
</ul>
</td>
<td>
<ul>
<li><a href="meta">Meta</a></li>
<li><a href="random">Random</a></li>
<li><a href="meta">meta</a></li>
<li><a href="random">random</a></li>
</ul>
</td>
<td>
<ul>
<li><a href="io">IO</a></li>
<li><a href="scheduler">Scheduler</a></li>
<li><a href="timer">Timer</a></li>
<li><a href="io">io</a></li>
<li><a href="scheduler">scheduler</a></li>
<li><a href="timer">timer</a></li>
</ul>
</td>
</tr>

2
doc/site/style.scss
View File

@ -209,7 +209,7 @@ h3:hover > .header-anchor:hover {
color: $link-dark;
}
p, li {
p {
margin: 10px 0;
}