Clean up npm distribution package to avoid uploading unnecessary files that developers don't need for using pumascript, such as: tracks, gruntfile and probably tests.

Run on CI.

We need to have an one dependency file. To achieve that we need migrate front-end dependencies to NPM.

https://github.com/emravera/retruco.git

• Separate pumascript.js into modules
• Create tasks for building a production version of the library, using requirejs optimizer

The value of a StatementList is not the value of the last value producing Statement in the StatementList as convened on the ECMA-262 Specification:

NOTE Steps 5 and 6 of the above algoritm ensure that the value of a StatementList is the value of the last value producing Statement in the StatementList. For example, the following calls to the eval function all return the value 1: "snip"

Related tests: test/suites/Tests-12-ECMA.js: [lines 15, 21, 28]

The in operator, as specified in the ECMA Standard [http://www.ecma-international.org/ecma-262/5.1/#sec-11.8.7], is not handled at runtime. E.g.:

var trees = ["redwood", "bay", "cedar", "oak", "maple"];
6 in trees;

awards you with:

[2, 0] binary operator "in" not found

Add documentation to all relevant interfaces, taking into account parameters and return types

Prepare an initialization process to install node modules, bower components and everything that can be needed to start developing/using pumascript.

Add support for conditional operators as defined in the ECMA Standard [http://www.ecma-international.org/ecma-262/5.1/#sec-11.12] E.g.:

false ? 'manzana' : 'naranja';

and nested conditional operators:

firstCheck ? "Access denied" : secondCheck ? "Access denied" : "Access granted";

Using the Function.prototype.bind() method [http://www.ecma-international.org/ecma-262/5.1/#sec-15.3.4.5] makes the process fail or doesn't return the object correctly. E.g.:

var scope = 'global';
var order = { scope: 'THIS', getScope: Function('return this.scope;') };
var unbound_scope = order.getScope;
var order_scope = unbound_scope.bind(order);
order_scope();

or

this.x = 9; 
var module = {
  x: 81,
  getX: function() { return this.x; }
};

var retrieveX = module.getX;

var boundGetX = retrieveX.bind(module);
boundGetX();

The Object.prototype.toString() method, when called, should return the following:

1. If the this value is undefined, return "[object Undefined]".
2. If the this value is null, return "[object Null]".
   (...)
   as specified in the ECMA Standard [http://www.ecma-international.org/ecma-262/5.1/#sec-15.2.4.2]

Calling the method with the this parameter set as either undefined or null values returns [object DOMWindow] E.g.:

Object.prototype.toString.call(undefined);

Upgrate to latest version the libraries of esprima and escodegen.

In other hand we need to have up to date all the current libraries in the project Take special care with phantomjs lib.

Build pumascript, distribute dist folder with some other files and exclude tests, tracks and editor folders between others.

Clean up and improve library modules. Define smaller and cohesive modules.

Implement visitor for TryStatement nodeType. E.g.:

try {
  console.log("try");
}
catch (excepcion) {
   console.log("catch");
}
finally {
  console.log("finally");
}

boolean native type handling throws TypeError on runtimejs.
E.g.:
var b = true; b.valueOf();
or
var b = true; b.toString();

When no key-value pair is stored in Local Storage, calling localStorage.getItem will resolve to null.
There's no check implemented so it's throwing an Exception when passed to Codemirror.

codemirror.js:1368 Uncaught TypeError: Cannot read property 'split' of null
at splitLinesAuto (codemirror.js:1368)
at Doc.splitLines (codemirror.js:6256)
at Doc. (codemirror.js:5906)
at Doc.setValue (codemirror.js:3879)
at CodeMirror$1.setValue (codemirror.js:9263)
at PumaEditor.setEditorValue (editor.js:68)
at PumaEditor.load (editor.js:72)

/** @meta */
function (){
}

https://github.com/emravera/retruco.git

When a variable is declared, without an initial value, it is initialised as null valued. E.g.
var a;

typeof a; a === null
> true

From the QUnit Documentation:

https://api.qunitjs.com/equal/#equal-actual-expected-message

equal( actual, expected [, message ] )

Description: A non-strict comparison, roughly equivalent to JUnit's assertEquals.
actual - Type: Object - Expression being tested
expected - Type: Object - Known comparison value
message - Type: String - A short description of the assertion

The equal assertion uses the simple comparison operator (==) to compare the actual and expected arguments. When they are equal, the assertion passes; otherwise, it fails. When it fails, both actual and expected values are displayed in the test result, in addition to a given message.

https://api.qunitjs.com/ok/#ok-state-message

ok( state [, message ] )

Description: A boolean check, equivalent to CommonJS's assert.ok() and JUnit's assertTrue(). Passes if the first argument is truthy.
state - Type: Expression - Expression being tested
message - Type: String - A short description of the assertion

The most basic assertion in QUnit, ok() requires just one argument. If the argument evaluates to true, the assertion passes; otherwise, it fails. If a second message argument is provided, it will be displayed in place of the result.

Meaning

The message arguments are actually optional and are supposed to reflect the purpose of the test. In our case the test suite should be reviewed and for every test this last argument either be removed or modified to serve the test objective.

nodeType "SequenceExpression" case has no visit method assigned at runtime.js.

Example of associated test:

function myFunc() { var x = 0; return (x+=1, x*=2, x); }
myFunc();

https://github.com/emravera/retruco.git

Start creating tests and comment them on the suites in order to have the complete test suite for JavaScript language in the runtime.

Create the initial wiki and the tutorial wiki.

Postfix Increment Operators¹ (lhs++) and Postfix Decrement Operators² (lhs--) do not respect the order of operation execution as defined by the ECMA-262v5.1 Standard:
1 - https://www.ecma-international.org/ecma-262/5.1/#sec-11.3.1
2 - https://www.ecma-international.org/ecma-262/5.1/#sec-11.3.2

E.g.:
var i = 1; var a = [false, false]; a[i--] = 1; a;
returns a = [1, false] instead of a = [false, 1] which a correct operation should result in.

and conditional expressions that expect such behaviour could result in infinite loops. Like:

var a = [null, null]; for(var i = 0; i < a.length; a[i++] = 0); a;

Make puma accesible using npm the puma module to be integrated in the CI infrastructure.

The current README.md could be improved in order to add a section for getting started, and then more information like we have today.

I would like available puma editor on the Cloud. That's easier to test and start playing than clone the project and run locally.

This feature could help to have a quick adoption by users.

Publish on the npm registry the puma task version 0.1 to be used by other developers. This will enable the tool to be easy integrated into the CI environments as it is today.

Performing binary expressions using the instanceof operator throws an exception. E.g.:

function C(){}
var a = new C();
a instanceof C;

or

function Car(make, model, year) {
  this.make = make;
  this.model = model;
  this.year = year;
}

var mycar = new Car("Honda", "Accord", 1998);
mycar instanceof Car;

Both throw

TypeError: invalid 'instanceof' operand rightResult.value

FirstPass.prototype.visitBinaryExpression() runtime.js:468
FirstPass.prototype.accept() runtime.js:88
FirstPass.prototype.accept() runtime.js:85
FirstPass.prototype.acceptArray() runtime.js:63
FirstPass.prototype.visitProgram() runtime.js:200
FirstPass.prototype.accept() runtime.js:82
FirstPass.prototype.run() runtime.js:70
evalPumaAst() runtime.js:933
evalPuma() runtime.js:928

The value returned by the [[Prototype]] internal property of the built-in object types when called is not properly handled, and thus remains undefined when used.

E.g.:

var persona = Object.create(Object.prototype, { name: { value: 'Nadia' } });

TypeError: undefined is not an object or null

Object.prototype.constructor;

TypeError: Cannot use 'in' operator to search for 'constructor' in undefined

When using user-defined object types the problem does not produce, e.g.:

function Car(make, model, year) {
  this.make = make;
  this.model = model;
  this.year = year;
}

Object.create(Car.prototype, { make: {value:'Tesla'}, model: {value:'S'}, year: {value:2016} });

Update the list of team members. Add to git page some hot topics like git flow. Create new entries to help new member in the ramp up.

I have a meta function calling another meta function and that's not working.
If i don't use the meta tag for the second function, it does work.

/**
 * @meta
 */
function alertSetIntervalVulnerability() {
    var newFunctionPuma = puma.pumaFindByType(pumaProgram, "ExpressionStatement");
    for (var index = 0; index < newFunctionPuma.length; index++) {
        findSetIntervalVulnerability(newFunctionPuma[index]);
    }
    return null;
}
/**
 * @meta
 */
function findSetIntervalVulnerability(setIntervalAst) {
    var expression = setIntervalAst.expression;
    if (expression.type === 'CallExpression') {
        var nombre = expression.callee.name;
        if (nombre === 'setInterval') {
            var parametro = expression.arguments[0];
            if (parametro.type === 'Literal') {
                console.log('La función setInterval que ha definido puede ser un potencial problema de seguridad');
            }
        }
    }
}

Using the delete operator to remove a property from an object doesn't work. E.g.:

s1 = Object({Name:'LEO', Terminal:25000, Destination:'Panchaea'});
delete s1.Destination;
Object.getOwnPropertyNames(s1);

Add shortcuts for the editor functions so they can be called through a key combination. E.g.

CTRL+X for executing the current code.
CTRL+L for loading saved state.

Useful for faster execution and would help when large pieces of code are introduced on the editor for testing.

Improve the saving of states to the local storage by making them more intuitive or providing a quick sum-up of the availability of this function. A save button for stashing the current state could also be provided.

The semantic declaration order is not respected in Pumascript. The testcase that must pass is the following one:

foo(2,3);

function foo(a, b) {
    return a + b;
}

Using the new operator to create an instance of a built-in object type throws a TypeError exception. E.g.
new Object();

FirstPass.visitNewExpression @ runtime.js:796

FirstPass.accept @ runtime.js:154
FirstPass.accept @ runtime.js:85
FirstPass.acceptArray @ runtime.js:63
FirstPass.visitProgram @ runtime.js:200
FirstPass.accept @ runtime.js:82
FirstPass.run @ runtime.js:70
evalPumaAst @ runtime.js:933
evalPuma @ runtime.js:928

Contrarily, creating instances of user-defined object types does not. E.g.

   function Car(make, model, year) {
     this.make = make;
     this.model = model;
     this.year = year;
   }

   var a = new Car('Tesla','S',2016);

Link to gitter.

GitHub Pages is an easy and rather complete way of documenting a repositories codebase, providing information about the project and releasing use examples and/or code samples.

Being integrated with the repository it's implementation is quite straightforward and easily maintainable:
How to publish, Docs Setting

It's features should be enough for the current implementation as a way of enhancing visibility, providing support and making puma-script more accesible and its use more encouraging.

Several result.success checks are missing from /tests/suites/Test-12-ECMA.js and possibly others.

The equal(result.success, true); assertion should be added to the missing tests.

Blank initialization, condition, and update block expressions for the ForStatement aren't supported.
All three of these expressions should be optional, as defined in the ECMA-262v5.1 Standard.

Related tests: test/suites/Tests-12-ECMA.js, lines 185 through 205.

Hello!

I want to do a obfuscation of JavaScript code. For now, I want to add a dummy variable in each for. The example is:

/* @meta */
function meta(){
    var forStatements = puma.pumaFindByType(pumaProgram, 'ForStatement');
    for(var k = 0; k < forStatements.length; k++){
        var forStatement = forStatements[k];
        var declarations = forStatement.init.declarations;
        declarations.push({
            id: {
                type: "Identifier",
                name: "j"
            },
            init: {
                type: "Literal",
                value: 3
            },
            type: "VariableDeclarator"
        });
    }
    return null;
}

The code works.

So, I have one question:
The meta functions are part of puma program so the for sentence inside in my meta function is analyzed too? How avoid this? I want to say, I don't want analyze the for sentence inside in my meta function.

I am using puma-editor for create this example...