Now THAT statement makes no sense to me.  Adding the single quote does
not affect any code, so why does this suggestion annoy you? Others have
made good points about preserving the ability to distinguish between
strings and characters (or some other kind of data), but you raise an
objection without providing a good reason for that objection.

On 9/29/2022 7:55 AM, edmund ronald wrote:

Who says the suggestion annoys me? I just don’t think it’s worth the pain
of changing the code, validating it, and one day realizing that some
teenage genius has found an injection bug that brings down a site that uses
openscad to generate parts.

Edmund

On Thursday, September 29, 2022, jon jon@jonbondy.com wrote:

At least now I understand what your objection is.  Thanks

On 9/29/2022 9:18 AM, edmund ronald wrote:

On 9/29/2022 7:52 AM, Michael Marx wrote:

Absolutely.

Since I've been working a lot in languages that allow both, and since my
work style guides call for single quotes in both of them, my typing
habits occasionally forget when I'm in OpenSCAD.

Summarizing the comments, and responding to them:

• Reserve for character type
  o Evaluates as a number?
  o I would like to think that OpenSCAD is a post-character-code
  language, one where character codes are available via chr() and
  ord() but are not a primary part of the language.  Programmers
  should not have to think about 97 meaning 'a', and should not be
  encouraged to think about it that way.
• World has too many options.
  o Yes, but conforming to what are arguably the #1 and #2
  programming languages in the world (and are certainly two of the
  top five or so) is arguably reducing the number of options.
• Leave well enough alone.
  o An excellent argument.
• Reserve for future syntax.
  o Hard to counter, other than that any such thing would be unique
  - and unique is bad.

There is no problem here.  There is no new feature here.  There is
arguably a minor usability improvement - improving alignment with common
languages and making typing microscopically easier.

(Yes, the typing improvement is microscopic.  However, it's a fairly
common thing to type... it's a bit hard to come up with any other change
that would affect usage so frequently.)

Anyhow, having raised the possibility and not heard a chorus of "oh,
yeah, that annoys me every day", I'm happy to drop it.

It annoys me every day, because I am used to using single quotes, but it
is only one of the many things about OpenSCAD which are annoying.

On 9/29/2022 12:08 PM, Jordan Brown wrote:

I read this thread bottom up (newer messages first) so I just wanted to
add that I think that  your 2nd point, "Can naturally embed one within
the other", is really saying that allowing both kinds of quotes makes
for more readable code, right? Natural (more readable) code is easier to
understand and less likely to contain errors.

I don't have a strong feeling on this either way but the issue has come
up for me in real life. A couple of us on this list are working on a 3D
braille library. My part is to write a script to convert space delimited
braille translation tables into a data structure in OpenSCAD code. Of
course, the quote itself is a valid braille character but worse, the
tables can contain quoted strings.

On 9/28/22 22:25, Jordan Brown wrote:

On 9/29/2022 9:22 AM, John Heim wrote:

Readable, type-able, et cetera.

I think it's a question of habit:

• Python people like having ' and ", but that's just a gateway to ''' and
  """ 😂
• JavaScript people like having ' and ", but what they really love is ` 😁
• C people don't even see the \ in " anymore 😅
• Unicode people may point out that you can ‟scare” someone without
  changing anything else
• Me? When this discussion arises (and it has, many times in many places) I
  like to add that in Spain we use « and » 😋

El jue, 29 sept 2022 a las 18:34, Father Horton (fatherhorton@gmail.com)
escribió:

--
Saludos,
Antonio