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

parse settings array instead of compiling them #449

Merged
merged 1 commit into from Aug 1, 2016

Conversation

@commy2
Copy link
Contributor

commy2 commented Jul 31, 2016

No description provided.

@commy2 commy2 added Enhancement WIP and removed WIP labels Jul 31, 2016
@@ -28,6 +28,30 @@ Author:
#define ASCII_ARRAY_OPEN (toArray "[" select 0)
#define ASCII_ARRAY_CLOSE (toArray "]" select 0)

private _fnc_parseArray = {

This comment has been minimized.

Copy link
@Killswitch00

Killswitch00 Aug 1, 2016

Contributor

The function takes a string as input, so _fnc_parseString?

This comment has been minimized.

Copy link
@commy2

commy2 Aug 1, 2016

Author Contributor

It's a stringified array. "[<...>]". parseNumber for example also takes and not

parseNumber "1"
-> 1

This comment has been minimized.

Copy link
@Killswitch00

Killswitch00 Aug 1, 2016

Contributor

Fair enough.

@Killswitch00 Killswitch00 merged commit 24e49c0 into master Aug 1, 2016
@commy2 commy2 deleted the settings-parse-array-method branch Aug 1, 2016
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Projects
None yet
2 participants
You can’t perform that action at this time.