Hi, 
Guest
Pic
Sign In

discuss@lists.openscad.org

OpenSCAD general discussion Mailing-list

View all threads

modules starting with a numeral q

GH
gene heskett
Thu, May 29, 2025 9:00 PM

On 5/29/25 01:54, Jordan Brown wrote:

Note that sequences with digits, an "e" or "E", and more digits, have
always been disallowed as identifiers, because they are numbers in
exponential form.

a module named 3dtouch() was legal a year ago, but sick bird and would
not re-render in the May '25 version. Not a show stopper as it was an ez
fix. Did catch me by surprise.

Thanks Jordan.

Take care of #1.

Cheers, Gene Heskett, CET.

--
"There are four boxes to be used in defense of liberty:
soap, ballot, jury, and ammo. Please use in that order."
-Ed Howdershelt (Author, 1940)
If we desire respect for the law, we must first make the law respectable.

  • Louis D. Brandeis
On 5/29/25 01:54, Jordan Brown wrote: > Note that sequences with digits, an "e" or "E", and more digits, have > always been disallowed as identifiers, because they are numbers in > exponential form. a module named 3dtouch() was legal a year ago, but sick bird and would not re-render in the May '25 version. Not a show stopper as it was an ez fix. Did catch me by surprise. Thanks Jordan. Take care of #1. Cheers, Gene Heskett, CET. -- "There are four boxes to be used in defense of liberty: soap, ballot, jury, and ammo. Please use in that order." -Ed Howdershelt (Author, 1940) If we desire respect for the law, we must first make the law respectable. - Louis D. Brandeis
MK
Marius Kintel
Thu, May 29, 2025 9:04 PM

On May 29, 2025, at 16:39, gene heskett gheskett@shentel.net wrote:

Thank you Marius. But the denial seems to have snuck in early and my year old code puked over it, prompting a conversion that eliminated a module named 3dtouch() in favor of mnt_3dtouch(), which then worked fine with the may '25 build.

OpenSCAD will halt on this warning if you have enabled Preferences->Advanced->OpenSCAD Language Features->Stop on the first warning. If you uncheck that box, your original code should keep working.

What was briefly discussed in the past (but hasn’t yet resulted in any actual work) was to look into ways of tuning the “Stop on the first warning” setting a bit to allow people to e.g. silence specific warnings as it appear this is a common feature to enable due to excessive warnings coming from other sources.

-Marius

On May 29, 2025, at 16:39, gene heskett <gheskett@shentel.net> wrote: > Thank you Marius. But the denial seems to have snuck in early and my year old code puked over it, prompting a conversion that eliminated a module named 3dtouch() in favor of mnt_3dtouch(), which then worked fine with the may '25 build. OpenSCAD will halt on this warning if you have enabled Preferences->Advanced->OpenSCAD Language Features->Stop on the first warning. If you uncheck that box, your original code should keep working. What was briefly discussed in the past (but hasn’t yet resulted in any actual work) was to look into ways of tuning the “Stop on the first warning” setting a bit to allow people to e.g. silence specific warnings as it appear this is a common feature to enable due to excessive warnings coming from other sources. -Marius
GH
gene heskett
Thu, May 29, 2025 9:18 PM

On 5/29/25 17:05, Marius Kintel via Discuss wrote:

On May 29, 2025, at 16:39, gene heskett gheskett@shentel.net wrote:

Thank you Marius. But the denial seems to have snuck in early and my year old code puked over it, prompting a conversion that eliminated a module named 3dtouch() in favor of mnt_3dtouch(), which then worked fine with the may '25 build.

OpenSCAD will halt on this warning if you have enabled Preferences->Advanced->OpenSCAD Language Features->Stop on the first warning. If you uncheck that box, your original code should keep working.

That is a rather normal setting I've had enabled for years. Points out
my typu's.

What was briefly discussed in the past (but hasn’t yet resulted in any actual work) was to look into ways of tuning the “Stop on the first warning” setting a bit to allow people to e.g. silence specific warnings as it appear this is a common feature to enable due to excessive warnings coming from other sources.

-Marius

OpenSCAD mailing list
To unsubscribe send an email to discuss-leave@lists.openscad.org

Cheers, Gene Heskett, CET.

"There are four boxes to be used in defense of liberty:
soap, ballot, jury, and ammo. Please use in that order."
-Ed Howdershelt (Author, 1940)
If we desire respect for the law, we must first make the law respectable.

  • Louis D. Brandeis
On 5/29/25 17:05, Marius Kintel via Discuss wrote: > On May 29, 2025, at 16:39, gene heskett <gheskett@shentel.net> wrote: >> Thank you Marius. But the denial seems to have snuck in early and my year old code puked over it, prompting a conversion that eliminated a module named 3dtouch() in favor of mnt_3dtouch(), which then worked fine with the may '25 build. > OpenSCAD will halt on this warning if you have enabled Preferences->Advanced->OpenSCAD Language Features->Stop on the first warning. If you uncheck that box, your original code should keep working. That is a rather normal setting I've had enabled for years. Points out my typu's. > > What was briefly discussed in the past (but hasn’t yet resulted in any actual work) was to look into ways of tuning the “Stop on the first warning” setting a bit to allow people to e.g. silence specific warnings as it appear this is a common feature to enable due to excessive warnings coming from other sources. > > -Marius > _______________________________________________ > OpenSCAD mailing list > To unsubscribe send an email to discuss-leave@lists.openscad.org Cheers, Gene Heskett, CET. -- "There are four boxes to be used in defense of liberty: soap, ballot, jury, and ammo. Please use in that order." -Ed Howdershelt (Author, 1940) If we desire respect for the law, we must first make the law respectable. - Louis D. Brandeis
JB
Jon Bondy
Thu, May 29, 2025 11:45 PM

Something like a list of error-message(or code)/line-number pairs, put
in a file with the same base name as the .SCAD file, but with a
different extension?  And perhaps a way to point to an error and add it
to this exception file?

On 5/29/2025 5:04 PM, Marius Kintel via Discuss wrote:

What was briefly discussed in the past (but hasn’t yet resulted in any actual work) was to look into ways of tuning the “Stop on the first warning” setting a bit to allow people to e.g. silence specific warnings as it appear this is a common feature to enable due to excessive warnings coming from other sources.

--
This email has been checked for viruses by AVG antivirus software.
www.avg.com

Something like a list of error-message(or code)/line-number pairs, put in a file with the same base name as the .SCAD file, but with a different extension?  And perhaps a way to point to an error and add it to this exception file? On 5/29/2025 5:04 PM, Marius Kintel via Discuss wrote: > What was briefly discussed in the past (but hasn’t yet resulted in any actual work) was to look into ways of tuning the “Stop on the first warning” setting a bit to allow people to e.g. silence specific warnings as it appear this is a common feature to enable due to excessive warnings coming from other sources. > -- This email has been checked for viruses by AVG antivirus software. www.avg.com
JB
Jordan Brown
Fri, May 30, 2025 12:15 AM

On 5/29/2025 4:45 PM, Jon Bondy via Discuss wrote:

Something like a list of error-message(or code)/line-number pairs, put
in a file with the same base name as the .SCAD file, but with a
different extension?  And perhaps a way to point to an error and add
it to this exception file?

The two obvious approaches are:

  • global-ish settings (GUI preferences, CLI options) that enable or
    disable particular warnings.
  • inline markup that says "don't bug me about <this warning> in this
    line".

Most C/C++ compilers/linters have both of those.

One could also imagine some sort of markup/pragma that says "don't bug
me about <this warning> with respect to <this symbol>", which would be
useful for this case but not for many others.

On 5/29/2025 4:45 PM, Jon Bondy via Discuss wrote: > Something like a list of error-message(or code)/line-number pairs, put > in a file with the same base name as the .SCAD file, but with a > different extension?  And perhaps a way to point to an error and add > it to this exception file? The two obvious approaches are: * global-ish settings (GUI preferences, CLI options) that enable or disable particular warnings. * inline markup that says "don't bug me about <this warning> in this line". Most C/C++ compilers/linters have both of those. One could also imagine some sort of markup/pragma that says "don't bug me about <this warning> with respect to <this symbol>", which would be useful for this case but not for many others.
Empathy v1.0   2025 ©emwd.com
Documentation