admin/mruby-mruby
1
0
Fork 0
mirror of https://github.com/mruby/mruby synced 2026-06-08 16:11:16 +00:00
Code Issues Packages Projects Releases Wiki Activity

Merge pull request #2773 from syohex/fix-misspelling

Browse Source 
Fix misspellings in document
This commit is contained in:
Yukihiro "Matz" Matsumoto
2015-04-27 21:54:25 +09:00
parent 5c25a9a6a9 c261c01598
commit 41e6931987
5 changed files with 6 additions and 6 deletions
Download Patch File Download Diff File Expand all files Collapse all files
doc/api/mruby.h.md
+1 -1
View File
@@ -49,7 +49,7 @@ It returns number of function retrieved.
char|mruby type|retrieve types|note
:---:|----------|--------------|---
`o`|`Object`|`mrb_value`|Could be used to retreive any type of argument
`o`|`Object`|`mrb_value`|Could be used to retrieve any type of argument
`C`|`Class`/`Module`|`mrb_value`|
`S`|`String`|`mrb_value`|
`A`|`Array`|`mrb_value`|
doc/compile/README.md
+2 -2
View File
@@ -245,7 +245,7 @@ mruby can use C++ exception to raise exception internally.
It is called C++ ABI mode.
By using C++ exception it can release C++ stack object correctly.
Whenever you mix C++ code C++ ABI mode would be enabled automatically.
If you need to enable C++ ABI mode explicity add the following:
If you need to enable C++ ABI mode explicitly add the following:
```ruby
conf.enable_cxx_abi
```
@@ -409,7 +409,7 @@ like this:
An extra directory is created for the target platform. In case you
compile for *i386* a directory called *i386* is created under the
build direcotry.
build directory.
The cross compilation workflow starts in the same way as the normal
compilation by compiling all *native* libraries and binaries.
doc/debugger/README.md
+1 -1
View File
@@ -144,7 +144,7 @@ Example:
(foo.rb:1) continue 3
```
This will resume the profram and stop it at the third breakpoint.
This will resume the program and stop it at the third breakpoint.
#### Delete Command
doc/mrbconf/README.md
+1 -1
View File
@@ -3,7 +3,7 @@
## How to use these macros.
You can use mrbconfs with following ways:
* Write them in `mrbconf.h`.
* Using compiler flags is prefered when building a cross binaries or multiple mruby binaries
* Using compiler flags is preferred when building a cross binaries or multiple mruby binaries
since it's easier to use different mrbconf per each `MRuby::Build`.
* Most flags can be enabled by just commenting in.
* Pass them as compiler flags.
doc/mrbgems/README.md
+1 -1
View File
@@ -200,7 +200,7 @@ the following options additionally inside of your GEM specification:
* `spec.test_objs` (Object test files for integration into mrbtest)
* `spec.test_preload` (Initialization files for mrbtest)
### include_paths and depencency
### include_paths and dependency
Your GEM can export include paths to another GEMs that depends on your GEM.
By default, `/...absolute path.../{GEM_NAME}/include` will be exported.