Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Missing string functions + other fixes #35

wants to merge 59 commits into
base: master


Copy link

@florentpoujol florentpoujol commented Nov 25, 2013


I added the missing string functions : find, format, gsub, gmatch and match.
All cases of pattern translation I encountered are working OK (yet there are probably many cases that won't).

I also fixed several other functions like ensure_arraymode(), pairs(), tonumber(), os.clock().

florentpoujol added 30 commits Oct 21, 2013
…ng (only partial support, several cases will not work)
…herever there is other characters than digits, dots or spaces in the input string (like Lua's tonumber() does)
… in the pattern (like I did on november 9 with lua_gmatch_next() )
…ad of an array (no matter the arraymode property)
Copy link

@florentpoujol florentpoujol commented Dec 11, 2013

Resume of what I did since the last batch of commits :

  • Fixed all styles issues as reported (braces, inline var declaration, etc...). (note that lua_add, lua_substract & Co are doing some inline variable declaration).
  • Improved some patterns, made unsupported patterns to call not_supported()
  • Added very partial support for the %b pattern (it's supported when it's the only item in a pattern).
  • Fixed a lot of bugs in the string functions

The cases where I had table.arraymode set to true but table.uints as object is fixed. It was due to another technology (CraftStudio's web player) that would add arraymode itself, yet left table.uints as an object.

I am new to node.js and I couldn't find how to run the tests in the "tests" folder. Which is why I hadn't them included in the pull request yet. Can you explain ?

Thanks !

Copy link

@elisee elisee commented Jan 8, 2014

@florentpoujol looking at the package.json file, you should be able to run the tests with npm run test.

Copy link

@florentpoujol florentpoujol commented Jan 8, 2014

@mherkender Hey, can you find time to review my latest commits ? Thanks !

Copy link

@florentpoujol florentpoujol commented Oct 18, 2014

Maybe it's time to do something about these improvements ?

They have been used without issues in several of my projects.
The Travis CI build failed but apparently because of Node itself, not because a test failed.
So I am not sure what I can do from here...

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
None yet
Linked issues

Successfully merging this pull request may close these issues.

None yet

4 participants