Skip to content

Commit ef26288

Browse files
committed
less awkward wording
1 parent c803f3d commit ef26288

1 file changed

Lines changed: 14 additions & 14 deletions

File tree

README.md

Lines changed: 14 additions & 14 deletions
Original file line numberDiff line numberDiff line change
@@ -6,9 +6,10 @@ compiler to PHP.
66
## Status
77

88
CoffeeScript version **1.3.1** has been fully ported over (see
9-
[tags](http://github.com/alxlit/coffeescript-php/tags)). Compiled code nearly
10-
matches the reference 100%, except for one or two benign differences (for
11-
example [#11](https://github.com/alxlit/coffeescript-php/issues/11)).
9+
[tags](http://github.com/alxlit/coffeescript-php/tags)). There are a couple
10+
benign differences between the port's compiled code and the reference's (for
11+
example [#11](https://github.com/alxlit/coffeescript-php/issues/11)), otherwise
12+
they match 100%.
1213

1314
## Requirements
1415

@@ -33,9 +34,8 @@ CoffeeScript\Init::load();
3334
## Usage
3435

3536
The API is really basic (single `compile($coffee, $options = NULL)` function).
36-
I don't plan on expanding it further (keep it simple).
37-
38-
Available options:
37+
I don't plan on expanding it further (keeping it simple). Here are the available
38+
options:
3939

4040
* **filename** - The source filename, formatted into error messages
4141
* **header** - Add a "Generated by..." header
@@ -73,17 +73,17 @@ clone the repository somewhere Apache can see it and navigate to tests/.
7373
#### What was the motivation for this project?
7474

7575
I was using PHP a lot at the time and wanted to use, learn more about, and
76-
potentially contribute back to the CoffeeScript project. I thought it'd be nice
77-
to have a native version gave it a shot.
76+
potentially contribute to the CoffeeScript project. I thought it'd be nice to
77+
have a native version gave it a shot.
7878

7979
#### Why not modify the original compiler to emit PHP?
8080

81-
The compiler itself depends on Jison, which is written in JavaScript, so you'd
82-
have to do something about that... More generally speaking, it'd be much more
83-
work to try and sort out all the differences between JavaScript and PHP (object
84-
model, core classes/libraries, etc), I imagine. There's also much less incentive
85-
to do all that work server side, where the choice to not use one language is,
86-
if not easy, at least available.
81+
For a number of reasons... First, I don't know why you'd want something like
82+
that. If you find PHP intolerable, just don't use it... Second, the original
83+
compiler depends on Jison, which is written in JavaScript, so you'd have to do
84+
something about that. Third, I think it'd be much more work to try and sort out
85+
all the differences between JavaScript and PHP (object model, core classes
86+
and libraries, etc).
8787

8888
#### What parser generator are you using?
8989

0 commit comments

Comments
 (0)