@@ -22,7 +22,7 @@ This is an experimental native compiler/backend for [PureScript](https://github.
22* PureScript arrays are implmented using [`std::deque`](http://en.cppreference.com/w/cpp/container/deque) (random access *O(1)*)
22* PureScript arrays are implmented using [`std::deque`](http://en.cppreference.com/w/cpp/container/deque) (random access *O(1)*)
23* `String` types are implmented using either C-strings (for literals) or `std::string`
23* `String` types are implmented using either C-strings (for literals) or `std::string`
24* `Number` is C++ `double`, `Int` is C++ `int`, `Char` is `char`, `Boolean` is `bool`
24* `Number` is C++ `double`, `Int` is C++ `int`, `Char` is `char`, `Boolean` is `bool`
25−* [Standard packages currently building (lightly tested)](https://github.com/andyarvanitis/pure11/wiki/Packages)
25+* [The current tested/supported package set is here.](https://github.com/pure11/package-sets/blob/psc-0.10.2/packages.json) Please feel free to submit a PR if you've had success with any others.
27#### TO-DO:
27#### TO-DO:
@@ -105,14 +105,14 @@ This assumes you are running OS X or a Unix-like system (Linux, *BSD, etc.), and
1063. Create a working directory wherever you like, and a `src` subdirectory under it, which will be where you will place your own PureScript source files.
1063. Create a working directory wherever you like, and a `src` subdirectory under it, which will be where you will place your own PureScript source files.
108−4. From your working directory, run the `{installation_path}/pcc` command with no arguments. This will generate a default `Makefile` for you in that directory. You can edit it if needed to change things like the location of the PureScript packages you intend to download and use. There are also some usage notes in the `Makefile` itself.
108+4. From your working directory, run the `{installation_path}/pcc` command with no arguments. This will generate `Makefile` and `psc-package.json` files in that directory. There are some usage notes in the generated `Makefile`.
110−5. Pull in your desired PureScript packages using `git` (bower will be supported later), making sure to use the pure11-specific versions in [this list](https://github.com/andyarvanitis/pure11/wiki/Packages).
110+5. Use PureScript's standard `psc-package` utility to add and manage package dependencies.
1126. You should now be ready to build a PureScript program.
1126. You should now be ready to build a PureScript program.
113 * 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.
113 * 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.
115− * To use the garbage collector, add `GC=yes` to the `make` command line (or you can modify the `Makefile` that you generated in step 4).
115+ * **Optional and advanced**: To use the garbage collector, add `GC=yes` to the `make` command line (or you can modify the `Makefile` that you generated in step 4).
117 * 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).
117 * 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).