The following are parts of my lib Scadx :
https://bitbucket.org/runsun/scadx/src/master/>>> Full featured map (aka dictionary) functionality (can't speak to
performance...) through global functions.
A hash based on search() could be very efficient:
https://github.com/runsun/OpenSCAD_Tips/blob/master/snippets.md#hashThis hash is heavily used though out the entire lib. For more hash-related
functions, see:
https://bitbucket.org/runsun/scadx/src/master/scadx_hash.scad>>> Type safety, a compiler or type checker could prevent me from making
>>> lots
of mistakes
A lot of type-checking functions (including geometric type like point etc):
https://bitbucket.org/runsun/scadx/src/master/scadx_inspect.scad>>> The ability to throw exceptions, and be informed where in the code the
exception occurred (like a stack trace)
I haven't visited this file for a long time:
https://bitbucket.org/runsun/scadx/src/master/scadx_error.scadThe stack tracing doesn't seem to be possible in OpenSCAD. But, a
tree-structure logging system might help:
https://bitbucket.org/runsun/scadx/src/master/scadx_log.scadCheck this out for demo:
https://bitbucket.org/runsun/scadx/src/master/demos/demo_log.scadAlso check these for your other interests:
https://bitbucket.org/runsun/scadx/src/master/scadx_array.scadhttps://bitbucket.org/runsun/scadx/src/master/scadx_range.scad>>> Modularity: the ability to tie things together (data for sure, but also
functions) in objects.
I've tried to construct some data structures to represent objects, packed
with all object properties and steps required to move/modify it, then use a
Make(data) module to draw it. The packaging makes it feel like
a class in OOP obj and allows it to be passed around, but since everything
is packed, it's extremely difficult to debug. The codes are still there:
https://bitbucket.org/runsun/scadx/src/master/scadx_make.scadbut I've walked away from it.
I do applied some data "packaging" (in a hash) to represent func/mod
arguments. This allow users to design a mod:
module Mymod( len,w, opt ) { ... }
then use it anyway like:
Mymod( len=3, w=4 );
Mymod( opt=["len", 3, "w",4] );
Mymod( w=5, opt=["len", 3, "w",4] ); // 5 would replace 4
and the opt can be passed around and updated at RT:
Mymod1( opt );
Mymod2( w=8, opt );
Mymod3( len=10, opt );
It also allows users to set/modify the properties of a sub-unit of an
object:
module Arm( len, d, opt ) { ... };
Arm( len=10, d=1 );
module Body( leg, arm, opt ) { ... } ;
Body( arm = arm_opt ); // where arm_opt = ["len",10, "d",1]
In this case, you can't do Arm( len=10, d=1) any more because Arm is inside
the Body.
The code :
https://bitbucket.org/runsun/scadx/src/master/scadx_args.scad-----
$ Runsun Pan, PhD $ libs: scadx , doctest , faces ( git ), offline doc ( git ), runscad.py ( 2 , git ), editor of choice: CudaText ( OpenSCAD lexer ); $ Tips ; $ Snippets
--
Sent from:
http://forum.openscad.org/_______________________________________________
OpenSCAD mailing list
[hidden email]
http://lists.openscad.org/mailman/listinfo/discuss_lists.openscad.org
Locked
