this will be compatible (there will be a block that converts ESL to snap code) with snap! and in snap there isn't really a distinction between chars and text.
aaa! did you read this?
if that's not the reason, what is
[reason]
because other programming languages use it
[/reason]
so? are we trying to imitate other programming languages?
i personally think it's redundant because you can just use strings
this is being done in snap, with as little JS as possible.
Characters are not the same thing as strings, sure, you can use strings as a workaround for characters, but they are not the same thing
characters are literally just strings, but more limiting! why would you use them?
besides
Why would you want that? That's an horrible idea!
In low level programming chars are just ascii codes and strings are pointers to arrays.
Most high-level languages only have a string type though.
Scheme, the only high level language, has two types, partly because strings and arrays have a lot of the same operators: item n of, append, etc.
C style that we don't want 
Why?
Because instead of having a zillion little ad hoc features, it takes full advantage of the power of procedures as an abstraction mechanism. And also, surprisingly considering its roots, it was the first language to get numbers right, making exactness orthogonal to representation, so you could create an exact float or an inexact integer if that correctly describes the source of the data.
Longer answer: Read SICP.
exactly; it doesn't make sense to have a whole nother type if you can very easily AND visually easy to work around.
(already 66 posts?)
bump
create script variable "a nice var" with null # (None is much better here)
create script variable "x" with 0
do {
change "a nice var" to [a nice var]+1
set "x" to [x]+1
}
while [x] greater than 1
display [a nice var]
I hope this should look ok?
SET
WITH THE VALUE
""
right?