I don't see any issues on the subject at https://github.com/openscad/openscad/issues , suggesting that nobody has been really interested.  You should file an issue if it's important to you, but of course that wouldn't guarantee that anybody *else* is interested and willing to do the work. Some notes: * A debugger would likely not be nearly as useful as you might think, because OpenSCAD doesn't put the model on the screen until after the program has executed - and can't, because there's no telling what will happen to any particular piece of geometry until it gets all the way to the top-level implied union. * The * and ! modifiers are also quite helpful.  So is #, but in a different way. * Note that echo() can be used in expressions, and that assert() can be used both as a statement and in an expression.

I understand what you're saying re the model displaying, but multiple times I've been attempting to troubleshoot looping and navigating through a complex if structure in a module.  I know what the model was going to look like when it finished; how it was getting there was what I was interested in.  Adding echos was becoming quite troublesome.  As it turned out in my case, I was able to color the different components and discover the errant if clause that was causing me trouble...this time. So I guess the question is what evidence do I need to provide to support the need for debugging tools to be added to the code editor?  Alternatively, isn't there a way to integrate a pre-developed open source IDE into OpenSCAD that would provide all those tools?  I know I make it sound trivial, but it just seems like an effort to reinvent the wheel here. Just a thought...don't shoot the newbie.  ;o) Bill Lugg On 10/17/22 16:28, Jordan Brown wrote: > I don't see any issues on the subject at > https://github.com/openscad/openscad/issues , suggesting that nobody > has been really interested.  You should file an issue if it's > important to you, but of course that wouldn't guarantee that anybody > *else* is interested and willing to do the work. > > Some notes: > > * A debugger would likely not be nearly as useful as you might > think, because OpenSCAD doesn't put the model on the screen until > after the program has executed - and can't, because there's no > telling what will happen to any particular piece of geometry until > it gets all the way to the top-level implied union. > * The * and ! modifiers are also quite helpful.  So is #, but in a > different way. > * Note that echo() can be used in expressions, and that assert() can > be used both as a statement and in an expression. > >