Empathy List Archives

V

vulcan_@mac.com

Fri, Aug 8, 2025 3:35 PM

There is a PR in progress https://github.com/openscad/openscad/pull/5942

that informed me about the Group() Module

but it does not offer completion of arguments in the editor and i do not find any preliminary docs on the WIP page in the docs nor in github

i would like to document it .. can anyone take time to give me the basics ?

is it to support the parent-child hierarchy? or is it creating something diff?

the name argument is just now being added, but what other args does it have?

There is a PR in progress https://github.com/openscad/openscad/pull/5942 that informed me about the Group() Module but it does not offer completion of arguments in the editor and i do not find any preliminary docs on the WIP page in the docs nor in github i would like to document it .. can anyone take time to give me the basics ? is it to support the parent-child hierarchy? or is it creating something diff? the name argument is just now being added, but what other args does it have?

TP

Torsten Paul

Fri, Aug 8, 2025 3:39 PM

On 08.08.25 17:35, vulcan_--- via Discuss wrote:

i would like to document it .. can anyone take time to give me the basics ?

Please don't. This is leaking internal data, and not allowed
in the official API.

If you want to document, the note should be: For internal use
only.

ciao,
Torsten.

On 08.08.25 17:35, vulcan_--- via Discuss wrote: > i would like to document it .. can anyone take time to give me the basics ? Please don't. This is leaking internal data, and not allowed in the official API. If you want to document, the note should be: For internal use only. ciao, Torsten.

RW

Rogier Wolff

Fri, Aug 8, 2025 3:49 PM

On Fri, Aug 08, 2025 at 05:39:34PM +0200, Torsten Paul via Discuss wrote:

On 08.08.25 17:35, vulcan_--- via Discuss wrote:

i would like to document it .. can anyone take time to give me the basics ?

Please don't. This is leaking internal data, and not allowed
in the official API.

If you want to document, the note should be: For internal use
only.

Shouldn't the name then be something like __group () to signify
internal use?

I mean if I have module creating a "group" of what I'm working on, I
might call it that. This might clash, especially when it is in an
include file that I forgot to include.

Or when the internal use ends up calling my redefined group module
expecting the builtin version.

(Best catch such things early before a change becomes cumbersome....)

Roger.

--
** R.E.Wolff@BitWizard.nl ** https://www.BitWizard.nl/ ** +31-15-2049110 **
** Verl. Spiegelmakerstraat 37 2645 LZ Delfgauw, The Netherlands.
** KVK: 27239233 **
f equals m times a. When your f is steady, and your m is going down
your a** is going up. -- Chris Hadfield about flying up the space shuttle.
** 'a' for accelleration.

On Fri, Aug 08, 2025 at 05:39:34PM +0200, Torsten Paul via Discuss wrote: > On 08.08.25 17:35, vulcan_--- via Discuss wrote: > > i would like to document it .. can anyone take time to give me the basics ? > > Please don't. This is leaking internal data, and not allowed > in the official API. > > If you want to document, the note should be: For internal use > only. Shouldn't the name then be something like __group () to signify internal use? I mean if I have module creating a "group" of what I'm working on, I might call it that. This might clash, especially when it is in an include file that I forgot to include. Or when the internal use ends up calling my redefined group module expecting the builtin version. (Best catch such things early before a change becomes cumbersome....) Roger. -- ** R.E.Wolff@BitWizard.nl ** https://www.BitWizard.nl/ ** +31-15-2049110 ** ** Verl. Spiegelmakerstraat 37 2645 LZ Delfgauw, The Netherlands. ** KVK: 27239233 ** f equals m times a. When your f is steady, and your m is going down your a** is going up. -- Chris Hadfield about flying up the space shuttle. ** 'a' for accelleration.

TP

Torsten Paul

Fri, Aug 8, 2025 3:57 PM

On 08.08.25 17:49, Rogier Wolff wrote:

(Best catch such things early before a change becomes cumbersome....)

Well, that would have been about 15 years ago, I suppose.

ciao,
Torsten.

On 08.08.25 17:49, Rogier Wolff wrote: > (Best catch such things early before a change becomes cumbersome....) Well, that would have been about 15 years ago, I suppose. ciao, Torsten.

JB

Jordan Brown

Fri, Aug 8, 2025 4:04 PM

On 8/8/2025 8:49 AM, Rogier Wolff via Discuss wrote:

Shouldn't the name then be something like __group () to signify
internal use?

I mean if I have module creating a "group" of what I'm working on, I
might call it that. This might clash, especially when it is in an
include file that I forgot to include.

Or when the internal use ends up calling my redefined group module
expecting the builtin version.

I don't think any of that can be a problem, except erroneously calling
it without defining your own.

It's used in CSG output to represent the nodes implied by module
invocations.

There shouldn't be anything, anywhere, that deliberately calls it, other
than included .csg files.

So if you define your own, and you include a .csg file, you might be
in trouble.

Most likely, if it ever became an issue we would get rid of it one way
or another.

On 8/8/2025 8:49 AM, Rogier Wolff via Discuss wrote: > Shouldn't the name then be something like __group () to signify > internal use? > > I mean if I have module creating a "group" of what I'm working on, I > might call it that. This might clash, especially when it is in an > include file that I forgot to include. > > Or when the internal use ends up calling my redefined group module > expecting the builtin version. I don't think any of that can be a problem, except erroneously calling it without defining your own. It's used in CSG output to represent the nodes implied by module invocations. There shouldn't be anything, anywhere, that deliberately calls it, other than included .csg files. So if you define your own, *and* you include a .csg file, you might be in trouble. Most likely, if it ever became an issue we would get rid of it one way or another.

V

vulcan_@mac.com

Sat, Aug 9, 2025 12:06 AM

Torsten Paul wrote:

On 08.08.25 17:35, vulcan_--- via Discuss wrote:

i would like to document it .. can anyone take time to give me the basics ?

Please don't. This is leaking internal data, and not allowed
in the official API.

Well .. it is already in the language, in the dev snapshot at least, so that when one starts the word “grou” the name completion informs me that a module by this name exists

So .. we should either document it as restricted and trust programmers to respect that .. or hide it to ensure the issue never arises

yes?

Torsten Paul wrote: > On 08.08.25 17:35, vulcan_--- via Discuss wrote: > > > i would like to document it .. can anyone take time to give me the basics ? > > Please don't. This is leaking internal data, and not allowed > in the official API. Well .. it is already in the language, in the dev snapshot at least, so that when one starts the word “grou” the name completion informs me that a module by this name exists So .. we should either document it as restricted and trust programmers to respect that .. or hide it to ensure the issue never arises yes?

discuss@lists.openscad.org

there is a group() module in dev snapshot - not fully implemented?