@@ -13,14 +13,13 @@ This is an experimental C++(11+)/native compiler backend for [PureScript](https:
13#### Differences from PureScript:
13#### Differences from PureScript:
15* Foreign imports are C++(11+) (or C) instead of JavaScript ([FFI examples](https://github.com/andyarvanitis/purescript-native/wiki/FFI_Examples))
15* Foreign imports are C++(11+) (or C) instead of JavaScript ([FFI examples](https://github.com/andyarvanitis/purescript-native/wiki/FFI_Examples))
16−* Compiler is `purecc` instead of `purs`, `make` is recommended for building
17* No C++-specific REPL
16* No C++-specific REPL
19#### Other notes:
18#### Other notes:
21* PureScript arrays are implemented using [`std::deque`](http://en.cppreference.com/w/cpp/container/deque) (random access *O(1)*)
20* PureScript arrays are implemented using [`std::deque`](http://en.cppreference.com/w/cpp/container/deque) (random access *O(1)*)
22* `String` types are implemented using either C-strings (for literals) or `std::string`
21* `String` types are implemented using either C-strings (for literals) or `std::string`
23−* `Number` is C++ `double`, `Int` is C++ `int`, `Char` is `std::string` (single utf-8 entity), `Boolean` is `bool`
22+* `Number` is C++ `double`, `Int` is C++ `int`, `Char` is `std::string` (single UTF-8 entity), `Boolean` is `bool`
25#### Future ideas:
24#### Future ideas:
@@ -44,13 +43,13 @@ If you're running macOS 10.13+ (High Sierra or later), you can avoid building it
453. Under your working directory, also create an `ffi` subdirectory, which will be where you will place your own C/C++ FFI source files.
443. Under your working directory, also create an `ffi` subdirectory, which will be where you will place your own C/C++ FFI source files.
47−4. Copy the [`Makefile`](https://github.com/andyarvanitis/purescript-native/blob/native-dump-corefn/support/Makefile) into your working directory.
46+4. Copy this [`Makefile`](https://github.com/andyarvanitis/purescript-native/blob/native-dump-corefn/support/Makefile) into your working directory.
49−5. Use PureScript's standard `psc-package` utility to add and manage package dependencies.
48+5. Use PureScript's standard [`psc-package]`(https://psc-package.readthedocs.io/en/latest/) utility to add and manage package dependencies.
516. You should now be ready to build a PureScript program.
506. You should now be ready to build a PureScript program.
52 * As stated above, place your source file(s) in the working directory's `src` subdirectory and execute `make`. If your machine has multiple cores, you might want to use `make -jN`, where `N` is the number of cores.
51 * As stated above, place your source file(s) in the working directory's `src` subdirectory and execute `make`. If your machine has multiple cores, you might want to use `make -jN`, where `N` is the number of cores.
54− * This will generate the C++ source tree for your program and then build an executable binary. The resulting executable will be in the `bin` subdirectory under the output directory and called `main` (so `output/bin/main`, by default). Source files will be in output/src/...
53+ * This will generate the C++ source tree for your program and then build an executable binary. The resulting executable will be in the `bin` subdirectory under the output directory and called `main` (so `output/bin/main`, by default). Source files will be in output/src/*