Unexpected POST_IF

Using most recent PRO nightly.

With very simple code:

unless smoother
   smoother = something()

I get the POST_IF error.

The same script is compiled perfectly in http://js2coffee.org/

More complicated code:

scrollHeader: (event, direction) ->
        nav = $ event.currentTarget
        unless smoother 
            smoother = $("<div/>").height(nav.height()).width(nav.width())
            nav.parent().parent().after(smoother) 

        smoother.toggle(direction is "up")
        nav.toggleClass('sticky', direction is "down")
        event.stopPropagation()

Is producing code like this:

_Class.prototype.scrollHeader = function(event, direction) {
      var nav, smoother;
      if (!smoother(smoother = $("<div/>").height(nav.height()).width(nav.width())(nav.parent().parent().after(smoother)(smoother.toggle(direction === "up")(nav.toggleClass('sticky', direction === "down")(event.stopPropagation())))))) {
        return nav = $(event.currentTarget);
      }
    };

I think this is because the editor is not inserting LFs correctly after "unless smoother". I can say this with certain confidence, because copying and pasting the code in a notepad editor produces a single line file without line feeds.

Also, when directly opening the file with Notepad, there are no LFs nor CRs. I have attached the file.

I also attached a screenshot of how the code looks in Visual Studio 2012. I have tried putting everything in a single line and inserting the new lines (ENTER), but for some reason it would appear the editor doesn't like it.

If I manually replace tabs for spaces, everything works as it should; however, that is not a good option for us; it seems that this is not an editor issue, but somehow when the code is streamed to the compiler, these lines get messed up.

thanks

I can confirm that this is some kind of editor buffer corruption (or parsing the output from said buffer).

I fixed this problem by opening the affected file (while open in Visual Studio) in another editor (Notepad2), inserting a space, and then saving it. VS prompted me to reload the file. After that was done, the compiled output was finally correct.

I now get a warning that my file has mixed spaces and tabs (which is not the case), but while the ouput is correct, I will live with that.

Thats interesting. If you are still able to recreate this can you zip up one of the offending files and send that over? I would be good to have a look to see what exactly was causing the issue. The file you attached earlier had mixed line endings but that wasnt causing a problem for compilation as far as I could see, I suspect something probably got stripped by the upload process though.

Jeremy