Empathy List Archives

not

1. Re: User Poll: What do you want to see from OpenSCAD
   development? (AKADAP)

module foo() {
    a = echo("foo assignment 1") 0;
    children(1);
    children(0);
    b = echo("foo assignment 2") 0;
}

foo() {
    x = echo("assignment 1") 0;
    echo("child 1");
    echo("child 2");
    echo("child 3");
    y = echo("assignment 2") 0;
}

 1. Re: User Poll: What do you want to see from OpenSCAD
    development? (AKADAP)

 module foo() {
      a = echo("foo assignment 1") 0;
      children(1);
      children(0);
      b = echo("foo assignment 2") 0;
 }

 foo() {
      x = echo("assignment 1") 0;
      echo("child 1");
      echo("child 2");
      echo("child 3");
      y = echo("assignment 2") 0;
 }

 Not sure that your example is a "normal use case" where variables
 might be helpful.
 I can not even visualize what you are trying to make.

 In my case, I only need the variables to persist from start to end
 and be acted on at some time during that period whenever an
 operation is requested that adds a component.
 If I add bunch of purchased or printed parts or a number of pipes
 of a certain length, I would like to generate a BOM
 24 part A
 47 part B
 3   Part C (custom part to print from a separate OpenSCAD used in
 the assembly)
 2     10 foot pipes
 20   2 foot pipes
 16   3 foot pipes
 and so on.

 When your project gets into the dozens of each part and there are
 100+ parts, the effort of redoing the count from a picture and the
 chance of missing a part both get high.

 Is there another/better way to tag objects created to enable a BOM
 to be generated at the end?
 If so, I could get a list of all tags created during the execution
 and then loop through the list and write ECHO "A count of all
 getTagName(i) is  getTagCount(i)"; at the end.
 During the creation of objects I would have to code something to
 say  "Tag this group of commands as a "Part A", "Tag this group as
 "Pipe_1.25_Inch-36" where 36 is some local value (*length*, width,
 diameter, etc.) used in the creation of the object.

 It does not solve all of the parametric design issues but would
 solve the BOM problem.

 Ron

 On 2020-04-04 7:26 p.m., Jordan Brown wrote:

 On 4/4/2020 3:49 PM, ken@volksswitch.org
 <mailto:ken@volksswitch.org> wrote:

 1) provide a Lint like feature () to help me identify modules that are never called and variables that are never used

 Note that as in lint itself there would need to be a way to mark
 a file as containing a library, since it's normal not to use all
 of the features exported by the library.

 2) allow a variable to be assigned a new value after it has already been assigned a value
 3) allow for a variable to be assigned a value in an if statement and then have that value preserved when the if completes

 I'm not one of the developers, but this is easy to answer:  not
 going to happen.  OpenSCAD doesn't execute anything like a
 conventional language.  It does *not* execute lines in the order
 that you expect. (And some features, like the children() feature,
 depend on that fact.)

 For fun, try this program.  Try to predict this output, then run
 it, then try to understand the results.

     module foo() {
          a = echo("foo assignment 1") 0;
          children(1);
          children(0);
          b = echo("foo assignment 2") 0;
     }

     foo() {
          x = echo("assignment 1") 0;
          echo("child 1");
          echo("child 2");
          echo("child 3");
          y = echo("assignment 2") 0;
     }

 For extra fun, try throwing $ variables into the mix.

 _______________________________________________
 OpenSCAD mailing list
 Discuss@lists.openscad.org  <mailto:Discuss@lists.openscad.org>
 http://lists.openscad.org/mailman/listinfo/discuss_lists.openscad.org

 -- 
 Ron Wheeler
 Artifact Software
 438-345-3369
 rwheeler@artifact-software.com  <mailto:rwheeler@artifact-software.com>

 _______________________________________________
 OpenSCAD mailing list
 Discuss@lists.openscad.org <mailto:Discuss@lists.openscad.org>
 http://lists.openscad.org/mailman/listinfo/discuss_lists.openscad.org

discuss@lists.openscad.org

Re: [OpenSCAD] Discuss Digest, Vol 65, Issue 2