preparser is too aggressive with strings

[jweather]

puts 'chord = foo' => Error: You may not use the built-in fn names as variable names. You attempted to use: chord

[samaaron]

yeah this is because I don't want user's writing (chord within their text as it will be transformed to chord( this potentially changing semantics which would be insane to track down. I'm therefore limiting the use of symbols which won't forego this transformation which is essentially every valid token in Ruby except the names of fns which return Rings in Sonic Pi's API.

[jweather]

I respectfully disagree... I should be able to put anything I like in a
string, and having SPi try to parse it is very confusing.
On Apr 21, 2015 5:49 PM, "Sam Aaron" notifications@github.com wrote:

yeah this is because I don't want user's writing (chord within their text
as it will be transformed to chord( this potentially changing semantics
which would be insane to track down. I'm therefore limiting the use of
symbols which won't forego this transformation which is essentially every
valid token in Ruby except the names of fns which return Rings in Sonic
Pi's API.

—
Reply to this email directly or view it on GitHub
#452 (comment).

[samaaron]

True, but I'm not sure we can accurately do that without an actual parser - which we'll hopefully have soon...

[samaaron]

With a parser we could just look for variable assignments directly :-)