Would be nice to have a composer-release with latest changes (1.3.1...master)

Thanks!

Hi ! first of all, thanks for you very very very very nice work, it's amazing and (very ?) useful !

I'd like to know if you can consider adding a package.json file, it makes life easier for us developer. if you don't know about that amazing tool, you can look at getcomposer.org and packagist.com. It can also be used to manage autoloading (but it requires php 5.3.2).

Anyway, thanks for your work !

Since version 1.4.0 of coffeescript is released i got some errors on the testcases...

i do not know if this errors are relevant for the compiled JS...

What's your opinion alxlit ?

src/CoffeeScript/yy/ Block.php line 42
"compile_block" should be "compile_node"

I am getting a E_Strict exception on a bunch of the methods on node classes thes first being yy_Access::constructor() not matching yy_Base::constructor().

The exact error(in kohana format) is ErrorException [ Strict ]: Declaration of CoffeeScript\yy_Access::constructor() should be compatible with CoffeeScript\yy_Base::constructor()

I am running Zend Server 5.6
PHP 5.4
OS X Lion

Am trying to modify the code myself but wanted to bring it to your attention

Also would like to say I love the project and thanks for all the work you put into it.

Hi Alex,

i read about debugging coffeescript and found this website
http://ryanflorence.com/2012/coffeescript-source-maps/

it seems that with the new CoffeeScriptRedux compiler it is possible to debug the coffee script.

so do you mean that you can port the source mapping to the php compiler?

greez

Is there any chance for this tool to support newer versions of coffeescript? The function chaining syntax has changed since 1.7.0, for example this:

$ '<div>'
    .appendTo foo

used to mean $('<div>'.appendTo(foo)), but since 1.7.0 it means $('<div>').appendTo(foo)

The test cases functions.coffee and function_invocations.coffee both fail for the 1.3.1 port of CoffeeScript, however this is due to a bug in the reference 1.3.1 compiler that has been fixed in the port, I think, (and in versions 1.3.2+ of the reference).

Here's the problem:

(splat..., @prop) ->

The reference 1.3.1 compiler will produce...

(function() {
  var __slice = [].slice;

  (function() {
    var splat, _i;
    splat = 2 <= arguments.length ? __slice.call(arguments, 0, _i = arguments.length - 1) : (_i = 0, []), prop = arguments[_i++];
    this.prop = prop;
  });
}).call(this);

...which fails to declare the prop variable. The port will correctly declare it, var prop, splat, _i;

Here is the script:

Ext.define "Some.Ext.class",
  initComponent: ->
    if "fdsfds"
      alert "fdsf"
      alert "fdsfds"

There is 500 error after that code compilation.

Example:

foo = 'bar' if something.kinda_stupidly.long \
        and blah.blah.baz is 'something'

What's the status on this project @alxlit? Has it reached a stand still as I'm curious about implementing it for a project where I'd like to avoid depending on the original compilers by default.

Cheers mate.

Hi !

Would it be complex to add a boolean option to control whether the generated Javascript is embedded in a self invoking function or not ? Currently this option doesn't exist, and sometimes it can be annoying to have this top self invoking function (for example, in a RequireJS application, this function is not needed).
(the JS Coffeescript compiler has chosen the bare option name for this functionnality)

Anyway, thanks for this great Coffeescript PHP library !

Besides just being nasty, this may cause trouble, since if the file is not included in global context, $UTILITIES will not make it into global namespace and therefore won't be available in the utility function.

This means, if someone - let's say it was me - loads coffeescript from within a class method, all the utilities are left out like in var __indexOf=; which will lead to a JavaScript parse error.

When I try to compile a blank file or a comment only file I get an error. Says:

unexpected YY_TERMINATOR

Hello,

How to create php code from coffee script ?

I want to use it, but how to steps needed.

How can I convert coffee script to php via command line ?

Kindly update me on this.

Thanks,

Placing a block comment in the middle of an object declaration sometimes breaks the coffeescript-php output, while the official coffee compiler handles them just fine.

Sample Coffee file

App.extend

    hello: ->
        "hi"

    ###
    Where Am I?

    This block comment will trigger a compiler bug.
    ###
    where_am_i: (location) ->
        "oh no!"

Result

(function() {
  App.extend({
    hello: function() {
      return "hi";
    }
  }, (function() {
    /*
        Where Am I?
    
        This block comment will trigger a compiler bug.
        */
  })(), {
    where_am_i: function(location) {
      return "oh no!";
    }
  });
}).call(this);

Reference Rendering, generated by coffee

(function() {

  App.extend({
    hello: function() {
      return "hi";
    },
    /*
        Where Am I?
    
        This block comment will trigger a compiler bug.
    */
    where_am_i: function(location) {
      return "oh no!";
    }
  });

}).call(this);

No pressing need for this to be fixed on my part, just reporting it. Nice work so far.

Hi there,

I recently tried out the current master to run some of our code on PHP7. I noticed a regression related to one of our source files. While being related to PHP7 the master version also fails to compile my code on PHP5.6

The reduced test case looks like this:

console.log 'foo' unless max > 0

Funny enough, this works:

console.log 'foo' unless max > 0#

I also tried 1.3.1 on PHP7 with the last commit 0dd2727 manually applied ('!==' to '!=' in Lexer.php). Same result.