Error when include file fails

classic Classic list List threaded Threaded
17 messages Options
Reply | Threaded
Open this post in threaded view
|

Error when include file fails

Brant Merryman
Hi. I'm a user of OpenSCAD and I also just happen to be a software developer with a lot of experience developing with Qt under C++.

I am interested in a feature of OpenSCAD and (to me) it seems like such an obvious and simple feature that I wanted to poll the OpenSCAD community to ask about it because perhaps there is some reason people don't want it to behave like this.

Basically, I would like OpenSCAD to generate an error and NOT render anything if I've called include or use and the file I've attempted to access isn't found. The reason I want this is because on a couple of occasions, people I work with have asked me "why does this part look wrong" or "why are the holes the wrong size"? And the reason is that they used OpenSCAD to compile/render a part, then exported it to STL, then generated gcode and printed it on our 3D printer only to realize that the file they compiled in OpenSCAD couldn't find the include file, so it used the default size for the holes, and then this caused the part to render incorrectly and now they've wasted a bunch of time and plastic, etc.

So, very straight forward issue. The fix for it should be fairly trivial. I'm quite prepared to fork OpenSCAD in github, make the change, test it, and then do a pull request, etc. to re-submit the change back to the OpenSCAD community. However, before I do that I want to ask whether this is a feature people want and if so, would you prefer that you be able to adjust this behavior in a setting? Is the current behavior actually needed by anyone?

Thanks.

Brant Merryman

_______________________________________________
OpenSCAD mailing list
[hidden email]
http://rocklinux.net/mailman/listinfo/openscad
http://openscad.org - https://flattr.com/thing/121566
Reply | Threaded
Open this post in threaded view
|

Re: Error when include file fails

Drew Rogge
+1. In fact I'd like it not to display anything if ANY error occurred. I don't know how many times
I've tried to figure out what's wrong with my geometry when what's really wrong is that there's a
misspelled variable and the error message is buried way up in the console window.

That and to give an error message when I try to export STL if I haven't "Compiled and Rendered <F6>"
since I changed the model.

Drew

On 04/10/2013 09:17 AM, Brant Merryman wrote:

> Hi. I'm a user of OpenSCAD and I also just happen to be a software developer with a lot of experience developing with Qt under C++.
>
> I am interested in a feature of OpenSCAD and (to me) it seems like such an obvious and simple feature that I wanted to poll the OpenSCAD community to ask about it because perhaps there is some reason people don't want it to behave like this.
>
> Basically, I would like OpenSCAD to generate an error and NOT render anything if I've called *include* or *use* and the file I've attempted to access isn't found. The reason I want this is because on a couple of occasions, people I work with have asked me "why does this part look wrong" or "why are the holes the wrong size"? And the reason is that they used OpenSCAD to compile/render a part, then exported it to STL, then generated gcode and printed it on our 3D printer only to realize that the file they compiled in OpenSCAD couldn't find the include file, so it used the default size for the holes, and then this caused the part to render incorrectly and now they've wasted a bunch of time and plastic, etc.
>
> So, very straight forward issue. The fix for it should be fairly trivial. I'm quite prepared to fork OpenSCAD in github, make the change, test it, and then do a pull request, etc. to re-submit the change back to the OpenSCAD community. However, before I do that I want to ask whether this is a feature people want and if so, would you prefer that you be able to adjust this behavior in a setting? Is the current behavior actually needed by anyone?
>
> Thanks.
>
> Brant Merryman
>
>
> _______________________________________________
> OpenSCAD mailing list
> [hidden email]
> http://rocklinux.net/mailman/listinfo/openscad
> http://openscad.org - https://flattr.com/thing/121566
_______________________________________________
OpenSCAD mailing list
[hidden email]
http://rocklinux.net/mailman/listinfo/openscad
http://openscad.org - https://flattr.com/thing/121566
Reply | Threaded
Open this post in threaded view
|

Re: Error when include file fails

kintel
Administrator
In reply to this post by Brant Merryman
On 2013-04-10, at 12:17 , Brant Merryman wrote:

>
> Basically, I would like OpenSCAD to generate an error and NOT render anything if I've called include or use and the file I've attempted to access isn't found.

It's a good idea.
It could use some discussion, but having the code for it makes sense.

The discussion is whether such (and other) errors should produce output or not, and if we should be able to override that functionality. Since I see openscad as somewhere between programming and description, sometimes I'd like to render whatever I can, and sometimes I want to abort with a clear error. Perhaps a flag (like -Werror in gcc) would make sense?

 -Marius

_______________________________________________
OpenSCAD mailing list
[hidden email]
http://rocklinux.net/mailman/listinfo/openscad
http://openscad.org - https://flattr.com/thing/121566
ds
Reply | Threaded
Open this post in threaded view
|

Re: Error when include file fails

ds
What about something like the Python approach, although it would break
your syntax?

In Python:
try:
     do_something()  or it could be include

except:
     do this if there is an error


This might be more consistent with OpenSCAD:

     try() {

         do_something()  or it could be include

     } except() {

         do this if there is an error

     }

Also, if there was an exit(), you could have a choice of a clean abort
on error.


On 04/10/13 09:49, Marius Kintel wrote:

> On 2013-04-10, at 12:17 , Brant Merryman wrote:
>
>> Basically, I would like OpenSCAD to generate an error and NOT render anything if I've called include or use and the file I've attempted to access isn't found.
> It's a good idea.
> It could use some discussion, but having the code for it makes sense.
>
> The discussion is whether such (and other) errors should produce output or not, and if we should be able to override that functionality. Since I see openscad as somewhere between programming and description, sometimes I'd like to render whatever I can, and sometimes I want to abort with a clear error. Perhaps a flag (like -Werror in gcc) would make sense?
>
>   -Marius
>
> _______________________________________________
> OpenSCAD mailing list
> [hidden email]
> http://rocklinux.net/mailman/listinfo/openscad
> http://openscad.org - https://flattr.com/thing/121566

_______________________________________________
OpenSCAD mailing list
[hidden email]
http://rocklinux.net/mailman/listinfo/openscad
http://openscad.org - https://flattr.com/thing/121566
Reply | Threaded
Open this post in threaded view
|

Re: Error when include file fails

Brant Merryman
When the include file is not found, what I see is:

WARNING: Can't find 'include' file 'foobar.scad'.

It seems to me like the cleanest way to implement this would be that in the Settings->Advanced, add a checkbox for "Treat Warnings as Errors". If this box is checked, the following changes in behavior:
1. Any warning that is encountered is treated as an error and prevents rendering.

Perhaps a second, related feature of removing the model on error could have a separate checkbox. Perhaps called "Remove Model on Error". If this box is checked, then if an error occurs, the model is removed from the screen and the user cannot accidentally export it as STL.

And a third feature, disallowing STL (or other types) of export, could be implemented with a checkbox that says "Prevent Export with Unsaved Changes" would force the model to compile if you have unsaved changes and try to do any kind of export.

Is this too much? For my purposes, I would always want all of these things turned on, but perhaps Marius has a different idea?

Marius mentioned a compiler flag ... we could certainly implement these as "compiler flags" and allow you to add them as "pragma"s within the code itself, or via some kind of "project file". Is there a vision for OpenSCAD to become some full blown IDE in the future, or is that something people want to intentionally avoid?

Also, I believe it is possible to invoke OpenSCAD from the command line, so I suppose anything that is added in the GUI would need to be added in the command line?




On Wed, Apr 10, 2013 at 12:04 PM, ds <[hidden email]> wrote:
What about something like the Python approach, although it would break
your syntax?

In Python:
try:
     do_something()  or it could be include

except:
     do this if there is an error


This might be more consistent with OpenSCAD:

     try() {

         do_something()  or it could be include

     } except() {

         do this if there is an error

     }

Also, if there was an exit(), you could have a choice of a clean abort
on error.


On 04/10/13 09:49, Marius Kintel wrote:
> On 2013-04-10, at 12:17 , Brant Merryman wrote:
>
>> Basically, I would like OpenSCAD to generate an error and NOT render anything if I've called include or use and the file I've attempted to access isn't found.
> It's a good idea.
> It could use some discussion, but having the code for it makes sense.
>
> The discussion is whether such (and other) errors should produce output or not, and if we should be able to override that functionality. Since I see openscad as somewhere between programming and description, sometimes I'd like to render whatever I can, and sometimes I want to abort with a clear error. Perhaps a flag (like -Werror in gcc) would make sense?
>
>   -Marius
>
> _______________________________________________
> OpenSCAD mailing list
> [hidden email]
> http://rocklinux.net/mailman/listinfo/openscad
> http://openscad.org - https://flattr.com/thing/121566

_______________________________________________
OpenSCAD mailing list
[hidden email]
http://rocklinux.net/mailman/listinfo/openscad
http://openscad.org - https://flattr.com/thing/121566


_______________________________________________
OpenSCAD mailing list
[hidden email]
http://rocklinux.net/mailman/listinfo/openscad
http://openscad.org - https://flattr.com/thing/121566
Reply | Threaded
Open this post in threaded view
|

Re: Error when include file fails

kintel
Administrator
On 2013-04-10, at 13:17 , Brant Merryman wrote:

> It seems to me like the cleanest way to implement this would be that in the Settings->Advanced, add a checkbox for "Treat Warnings as Errors". If this box is checked, the following changes in behavior:
[…]
> Perhaps a second,
[…]
> And a third feature,
[…]
>
> Is this too much? For my purposes, I would always want all of these things turned on, but perhaps Marius has a different idea?
>
I think it's on the right track, but perhaps keep fewer options, and think about that kind of micro control later on.

> Marius mentioned a compiler flag ... we could certainly implement these as "compiler flags" and allow you to add them as "pragma"s within the code itself, or via some kind of "project file". Is there a vision for OpenSCAD to become some full blown IDE in the future, or is that something people want to intentionally avoid?

By "compiler flag", I meant a simple flag which can be set in Preferences, as well as on the cmd-line.
I don't think we're going in the direction of an IDE. If anything, I think we'll go in the other direction in terms of native code (slim backend library), and move more in the direction of web for GUI/IDE.

> Also, I believe it is possible to invoke OpenSCAD from the command line, so I suppose anything that is added in the GUI would need to be added in the command line?
>
Exactly. The cmd-line options have been improved lately, and I foresee further improvement there.

 -Marius

_______________________________________________
OpenSCAD mailing list
[hidden email]
http://rocklinux.net/mailman/listinfo/openscad
http://openscad.org - https://flattr.com/thing/121566
Reply | Threaded
Open this post in threaded view
|

Re: Error when include file fails

Drew Rogge
A simple flag in Preferences or on the command line would work just fine for me.

On 04/10/2013 10:29 AM, Marius Kintel wrote:

> On 2013-04-10, at 13:17 , Brant Merryman wrote:
>
>> It seems to me like the cleanest way to implement this would be that in the Settings->Advanced, add a checkbox for "Treat Warnings as Errors". If this box is checked, the following changes in behavior:
> […]
>> Perhaps a second,
> […]
>> And a third feature,
> […]
>>
>> Is this too much? For my purposes, I would always want all of these things turned on, but perhaps Marius has a different idea?
>>
> I think it's on the right track, but perhaps keep fewer options, and think about that kind of micro control later on.
>
>> Marius mentioned a compiler flag ... we could certainly implement these as "compiler flags" and allow you to add them as "pragma"s within the code itself, or via some kind of "project file". Is there a vision for OpenSCAD to become some full blown IDE in the future, or is that something people want to intentionally avoid?
>
> By "compiler flag", I meant a simple flag which can be set in Preferences, as well as on the cmd-line.
> I don't think we're going in the direction of an IDE. If anything, I think we'll go in the other direction in terms of native code (slim backend library), and move more in the direction of web for GUI/IDE.
>
>> Also, I believe it is possible to invoke OpenSCAD from the command line, so I suppose anything that is added in the GUI would need to be added in the command line?
>>
> Exactly. The cmd-line options have been improved lately, and I foresee further improvement there.
>
>   -Marius
>
> _______________________________________________
> OpenSCAD mailing list
> [hidden email]
> http://rocklinux.net/mailman/listinfo/openscad
> http://openscad.org - https://flattr.com/thing/121566
_______________________________________________
OpenSCAD mailing list
[hidden email]
http://rocklinux.net/mailman/listinfo/openscad
http://openscad.org - https://flattr.com/thing/121566
Reply | Threaded
Open this post in threaded view
|

Re: Error when include file fails

nophead
I don't see why anybody would want it to carry on if a file was missing or there is a syntax error.


On 10 April 2013 19:49, Drew Rogge <[hidden email]> wrote:
A simple flag in Preferences or on the command line would work just fine for me.

On 04/10/2013 10:29 AM, Marius Kintel wrote:
> On 2013-04-10, at 13:17 , Brant Merryman wrote:
>
>> It seems to me like the cleanest way to implement this would be that in the Settings->Advanced, add a checkbox for "Treat Warnings as Errors". If this box is checked, the following changes in behavior:
> […]
>> Perhaps a second,
> […]
>> And a third feature,
> […]
>>
>> Is this too much? For my purposes, I would always want all of these things turned on, but perhaps Marius has a different idea?
>>
> I think it's on the right track, but perhaps keep fewer options, and think about that kind of micro control later on.
>
>> Marius mentioned a compiler flag ... we could certainly implement these as "compiler flags" and allow you to add them as "pragma"s within the code itself, or via some kind of "project file". Is there a vision for OpenSCAD to become some full blown IDE in the future, or is that something people want to intentionally avoid?
>
> By "compiler flag", I meant a simple flag which can be set in Preferences, as well as on the cmd-line.
> I don't think we're going in the direction of an IDE. If anything, I think we'll go in the other direction in terms of native code (slim backend library), and move more in the direction of web for GUI/IDE.
>
>> Also, I believe it is possible to invoke OpenSCAD from the command line, so I suppose anything that is added in the GUI would need to be added in the command line?
>>
> Exactly. The cmd-line options have been improved lately, and I foresee further improvement there.
>
>   -Marius
>
> _______________________________________________
> OpenSCAD mailing list
> [hidden email]
> http://rocklinux.net/mailman/listinfo/openscad
> http://openscad.org - https://flattr.com/thing/121566
_______________________________________________
OpenSCAD mailing list
[hidden email]
http://rocklinux.net/mailman/listinfo/openscad
http://openscad.org - https://flattr.com/thing/121566


_______________________________________________
OpenSCAD mailing list
[hidden email]
http://rocklinux.net/mailman/listinfo/openscad
http://openscad.org - https://flattr.com/thing/121566
Reply | Threaded
Open this post in threaded view
|

Re: Error when include file fails

Drew Rogge
Yeah, I'd just set the flag and forget it.

On 04/10/2013 11:57 AM, nop head wrote:
> I don't see why anybody would want it to carry on if a file was missing or there is a syntax error.
>
_______________________________________________
OpenSCAD mailing list
[hidden email]
http://rocklinux.net/mailman/listinfo/openscad
http://openscad.org - https://flattr.com/thing/121566
Reply | Threaded
Open this post in threaded view
|

Re: Error when include file fails

Peter Falke
In reply to this post by nophead
Hi,

one of the feedbacks seems to be that error/warnings go lost in the (small) console.
I sometimes wonder what the normal output really means and who actually uses (needs) it.
Maybe some of the lines could also be joined into one line (e.g.: Simple: yes   Valid: yes).


F5:
Module cache size: 0 modules

Compiling design (CSG Tree generation)...

Compiling design (CSG Products generation)...

PolySets in cache: 1

PolySet cache size in bytes: 2196

CGAL Polyhedrons in cache: 2

CGAL cache size in bytes: 29232

Compiling design (CSG Products normalization)...

Normalized CSG tree has 1 elements

CSG generation finished.

Total rendering time: 0 hours, 0 minutes, 0 seconds




F6:
Module cache size: 0 modules

Compiling design (CSG Tree generation)...

Rendering Polygon Mesh using CGAL...

PolySets in cache: 1

PolySet cache size in bytes: 2196

CGAL Polyhedrons in cache: 2

CGAL cache size in bytes: 29232

Top level object is a 3D object:

Simple: yes

Valid: yes

Vertices: 15

Halfedges: 66

Edges: 33

Halffacets: 40

Facets: 20

Volumes: 2

Total rendering time: 0 hours, 0 minutes, 0 seconds

Rendering finished.



Sincerely,

TakeItAndRun


On 10 April 2013 20:57, nop head <[hidden email]> wrote:
I don't see why anybody would want it to carry on if a file was missing or there is a syntax error.


On 10 April 2013 19:49, Drew Rogge <[hidden email]> wrote:
A simple flag in Preferences or on the command line would work just fine for me.

On 04/10/2013 10:29 AM, Marius Kintel wrote:
> On 2013-04-10, at 13:17 , Brant Merryman wrote:
>
>> It seems to me like the cleanest way to implement this would be that in the Settings->Advanced, add a checkbox for "Treat Warnings as Errors". If this box is checked, the following changes in behavior:
> […]
>> Perhaps a second,
> […]
>> And a third feature,
> […]
>>
>> Is this too much? For my purposes, I would always want all of these things turned on, but perhaps Marius has a different idea?
>>
> I think it's on the right track, but perhaps keep fewer options, and think about that kind of micro control later on.
>
>> Marius mentioned a compiler flag ... we could certainly implement these as "compiler flags" and allow you to add them as "pragma"s within the code itself, or via some kind of "project file". Is there a vision for OpenSCAD to become some full blown IDE in the future, or is that something people want to intentionally avoid?
>
> By "compiler flag", I meant a simple flag which can be set in Preferences, as well as on the cmd-line.
> I don't think we're going in the direction of an IDE. If anything, I think we'll go in the other direction in terms of native code (slim backend library), and move more in the direction of web for GUI/IDE.
>
>> Also, I believe it is possible to invoke OpenSCAD from the command line, so I suppose anything that is added in the GUI would need to be added in the command line?
>>
> Exactly. The cmd-line options have been improved lately, and I foresee further improvement there.
>
>   -Marius
>
> _______________________________________________
> OpenSCAD mailing list
> [hidden email]
> http://rocklinux.net/mailman/listinfo/openscad
> http://openscad.org - https://flattr.com/thing/121566
_______________________________________________
OpenSCAD mailing list
[hidden email]
http://rocklinux.net/mailman/listinfo/openscad
http://openscad.org - https://flattr.com/thing/121566


_______________________________________________
OpenSCAD mailing list
[hidden email]
http://rocklinux.net/mailman/listinfo/openscad
http://openscad.org - https://flattr.com/thing/121566



--
[hidden email]

P.S. Falls meine E-Mail kürzer ausfällt als Dir angenehm ist:
Ich probiere gerade aus kurze Antworten statt gar keine Antworten zu schreiben.
Wenn Du gerne mehr lesen möchtest, dann lass es mich bitte wissen.

P.S. In case my e-mail is shorter than you enjoy:
I am currently trying short replies instead of no replies at all.
Please let me know, if you like to read more.

Enjoy!

_______________________________________________
OpenSCAD mailing list
[hidden email]
http://rocklinux.net/mailman/listinfo/openscad
http://openscad.org - https://flattr.com/thing/121566
Reply | Threaded
Open this post in threaded view
|

Re: Error when include file fails

kintel
Administrator
On 2013-04-10, at 15:18 , Peter Falke wrote:

> one of the feedbacks seems to be that error/warnings go lost in the (small) console.
> I sometimes wonder what the normal output really means and who actually uses (needs) it.
> Maybe some of the lines could also be joined into one line (e.g.: Simple: yes   Valid: yes).
>
..and error summary (Errors: 4).

..or render errors in red
..or optionally turn off verbose output
..or stop on error, so that the error is always the last line.

There is no doubt that this can be improved a lot ;)

 -Marius
_______________________________________________
OpenSCAD mailing list
[hidden email]
http://rocklinux.net/mailman/listinfo/openscad
http://openscad.org - https://flattr.com/thing/121566
Reply | Threaded
Open this post in threaded view
|

Re: Error when include file fails

Len Trigg
I think allowing the render to continue just promotes insidious errors. A similar case is where you have a typo in one of your variable names. The only advantage I can see in continuing is so that you can collect multiple errors in one pass, not so you can look at the invalid rendered object.

Cheers,
Len.



On Thu, Apr 11, 2013 at 7:43 AM, Marius Kintel <[hidden email]> wrote:
On 2013-04-10, at 15:18 , Peter Falke wrote:

> one of the feedbacks seems to be that error/warnings go lost in the (small) console.
> I sometimes wonder what the normal output really means and who actually uses (needs) it.
> Maybe some of the lines could also be joined into one line (e.g.: Simple: yes   Valid: yes).
>
..and error summary (Errors: 4).

..or render errors in red
..or optionally turn off verbose output
..or stop on error, so that the error is always the last line.

There is no doubt that this can be improved a lot ;)

 -Marius
_______________________________________________
OpenSCAD mailing list
[hidden email]
http://rocklinux.net/mailman/listinfo/openscad
http://openscad.org - https://flattr.com/thing/121566


_______________________________________________
OpenSCAD mailing list
[hidden email]
http://rocklinux.net/mailman/listinfo/openscad
http://openscad.org - https://flattr.com/thing/121566
Reply | Threaded
Open this post in threaded view
|

Re: Error when include file fails

kintel
Administrator
On 2013-04-10, at 20:33 , Len Trigg wrote:

> I think allowing the render to continue just promotes insidious errors. A similar case is where you have a typo in one of your variable names. The only advantage I can see in continuing is so that you can collect multiple errors in one pass, not so you can look at the invalid rendered object.
>
Let's try to have a mode where OpenSCAD fails on errors (we can even try setting that mode as default).
The next step after that, is to define which of the current warnings warrants to be treated like such an error.

Brant: If you want to take a shot at this it would be awesome! If you need any info about getting started with the code, please get in touch.
A good starting point would be to collect a summary of this discussion into a github issue.

 -Marius

_______________________________________________
OpenSCAD mailing list
[hidden email]
http://rocklinux.net/mailman/listinfo/openscad
http://openscad.org - https://flattr.com/thing/121566
Reply | Threaded
Open this post in threaded view
|

Re: Error when include file fails

Brant Merryman
Thanks, Marius. I have entered an issue into github and I will take a crack at implementing it.


On Wed, Apr 10, 2013 at 11:04 PM, Marius Kintel <[hidden email]> wrote:
On 2013-04-10, at 20:33 , Len Trigg wrote:

> I think allowing the render to continue just promotes insidious errors. A similar case is where you have a typo in one of your variable names. The only advantage I can see in continuing is so that you can collect multiple errors in one pass, not so you can look at the invalid rendered object.
>
Let's try to have a mode where OpenSCAD fails on errors (we can even try setting that mode as default).
The next step after that, is to define which of the current warnings warrants to be treated like such an error.

Brant: If you want to take a shot at this it would be awesome! If you need any info about getting started with the code, please get in touch.
A good starting point would be to collect a summary of this discussion into a github issue.

 -Marius

_______________________________________________
OpenSCAD mailing list
[hidden email]
http://rocklinux.net/mailman/listinfo/openscad
http://openscad.org - https://flattr.com/thing/121566


_______________________________________________
OpenSCAD mailing list
[hidden email]
http://rocklinux.net/mailman/listinfo/openscad
http://openscad.org - https://flattr.com/thing/121566
Reply | Threaded
Open this post in threaded view
|

Re: Error when include file fails

Triffid Hunter
In reply to this post by nophead
On 11 April 2013 04:57, nop head <[hidden email]> wrote:
I don't see why anybody would want it to carry on if a file was missing

Greg Frost's extruders import STLs of his gears if they're present, for display purposes only. If they're absent, the warning is harmless

SO, we should have a way to treat it as an error, and have a way to get a mere warning if the import is only there for display purposes and isn't necessary for the actual output


perhaps %use or %import could trigger warning-only mode or something?

_______________________________________________
OpenSCAD mailing list
[hidden email]
http://rocklinux.net/mailman/listinfo/openscad
http://openscad.org - https://flattr.com/thing/121566
Reply | Threaded
Open this post in threaded view
|

Re: Error when include file fails

kintel
Administrator
On 2013-04-12, at 01:27 , Triffid Hunter wrote:
>
> Greg Frost's extruders import STLs of his gears if they're present, for display purposes only. If they're absent, the warning is harmless
>
Ah, the missing use-case - it always happens :)

> perhaps %use or %import could trigger warning-only mode or something?

syntactic sugar like that can be so confusing, but at least the % operator is already used for "background" rendering.

Also see https://github.com/openscad/openscad/issues/329 for a more concrete discussion.

 -Marius

_______________________________________________
OpenSCAD mailing list
[hidden email]
http://rocklinux.net/mailman/listinfo/openscad
http://openscad.org - https://flattr.com/thing/121566
Reply | Threaded
Open this post in threaded view
|

Re: Error when include file fails

Alan Cox
In reply to this post by Len Trigg
On Thu, 11 Apr 2013 12:33:02 +1200
Len Trigg <[hidden email]> wrote:

> I think allowing the render to continue just promotes insidious errors. A
> similar case is where you have a typo in one of your variable names. The
> only advantage I can see in continuing is so that you can collect multiple
> errors in one pass, not so you can look at the invalid rendered object.

There are cases its very useful to see if other bits worked. I'd agree
that an option is the way forward or perhaps even a leading character the
way debug etc are done that said "fail if this fails" or similar.

Alan
_______________________________________________
OpenSCAD mailing list
[hidden email]
http://rocklinux.net/mailman/listinfo/openscad
http://openscad.org - https://flattr.com/thing/121566