Endless warnings
Endless occurrences of:
variable something not specified as parameter
in the console/error list. The variables still work, it’s just a nuisance, as it changes the dimensions of the viewport.
Why does it do that and how can I get rid of it?
Google is your friend.
On Fri, Aug 19, 2022 at 7:24 PM mikeonenine@web.de wrote:
Endless occurrences of:
*variable *something not specified as parameter
in the console/error list. The variables still work, it’s just a nuisance,
as it changes the dimensions of the viewport.
Why does it do that and how can I get rid of it?
OpenSCAD mailing list
To unsubscribe send an email to discuss-leave@lists.openscad.org
[ Sorry for the duplicate, meant to reply to all. ]
On 8/19/2022 5:23 PM, mikeonenine@web.de wrote:
Endless occurrences of:
*variable */something/ not specified as parameter
in the console/error list. The variables still work, it’s just a
nuisance, as it changes the dimensions of the viewport.
Why does it do that and how can I get rid of it?
A sample program that demonstrates the problem would be helpful, as
would the exact text of the message with any following TRACE lines.
It looks to me like that message comes when you call a module or
function and supply a named parameter that the module or function is not
expecting.
For instance:
cylinder(xyzzy=3);
WARNING: variable xyzzy not specified as parameter in file , line 1
TRACE: called by 'cylinder' in file , line 1
The TRACE lines should point at the lines causing the problem.
Jordan Brown wrote:
[ Sorry for the duplicate, meant to reply to all. ]
On 8/19/2022 5:23 PM, mikeonenine@web.de wrote:
Endless occurrences of:
*variable */something/ not specified as parameter
in the console/error list. The variables still work, it’s just a
nuisance, as it changes the dimensions of the viewport.
Why does it do that and how can I get rid of it?
A sample program that demonstrates the problem would be helpful, as
would the exact text of the message with any following TRACE lines.
It looks to me like that message comes when you call a module or
function and supply a named parameter that the module or function is not
expecting.
For instance:
cylinder(xyzzy=3);
WARNING: variable xyzzy not specified as parameter in file , line 1
TRACE: called by 'cylinder' in file , line 1
The TRACE lines should point at the lines causing the problem.
The scripts where the warnings occur are often several hundred lines long, so I tried these as examples, expecting that they would produce warnings:
a=10;
b=20;
translate([b,0,0])
square([a,b]);
module sq()
{
square([x,y]);
}
translate([-b,0,0])
sq(x=10, y=20);
But they only produce the warning:
ERROR: Parser error: syntax error in file , line 8
Execution aborted
Curious in itself, as there is nothing in line 8, but the warnings I had hoped to provoke do not appear. So I need to take a closer look at an existing script that produces warnings to identify how and where they occur and work out a shorter example from that. May take a little time, in the meantime thanks for your response.
In module sq, there are no parameters x and y mentioned.
Maybe this could be the problem
Also you can tick the option stop on first warning in preferences
This will help detect the issue faster
On Sat, 20 Aug, 2022, 7:33 am , mikeonenine@web.de wrote:
Jordan Brown wrote:
[ Sorry for the duplicate, meant to reply to all. ]
On 8/19/2022 5:23 PM, mikeonenine@web.de wrote:
Endless occurrences of:
*variable */something/ not specified as parameter
in the console/error list. The variables still work, it’s just a nuisance,
as it changes the dimensions of the viewport.
Why does it do that and how can I get rid of it?
A sample program that demonstrates the problem would be helpful, as would
the exact text of the message with any following TRACE lines.
It looks to me like that message comes when you call a module or function
and supply a named parameter that the module or function is not expecting.
For instance:
cylinder(xyzzy=3);
WARNING: variable xyzzy not specified as parameter in file , line 1
TRACE: called by 'cylinder' in file , line 1
The TRACE lines should point at the lines causing the problem.
The scripts where the warnings occur are often several hundred lines long,
so I tried these as examples, expecting that they would produce warnings:
a=10;
b=20;
translate([b,0,0])
square([a,b]);
module sq()
{
square([x,y]);
}
translate([-b,0,0])
sq(x=10, y=20);
But they only produce the warning:
ERROR: Parser error: syntax error in file , line 8
Execution aborted
Curious in itself, as there is nothing in line 8, but the warnings I had
hoped to provoke do not appear. So I need to take a closer look at an
existing script that produces warnings to identify how and where they occur
and work out a shorter example from that. May take a little time, in the
meantime thanks for your response.
OpenSCAD mailing list
To unsubscribe send an email to discuss-leave@lists.openscad.org
I get
WARNING: variable x not specified as parameter in file openscad-2021.01, line 11
WARNING: variable y not specified as parameter in file openscad-2021.01, line 11
Back to the original, please post a few of the errors.
From: mikeonenine@web.de [mailto:mikeonenine@web.de]
Sent: Sat, 20 Aug 2022 12:03
To: discuss@lists.openscad.org
Subject: [OpenSCAD] Re: Endless warnings
Jordan Brown wrote:
[ Sorry for the duplicate, meant to reply to all. ]
On 8/19/2022 5:23 PM, mikeonenine@web.de wrote:
Endless occurrences of:
*variable */something/ not specified as parameter
in the console/error list. The variables still work, it’s just a nuisance, as it changes the dimensions of the viewport.
Why does it do that and how can I get rid of it?
A sample program that demonstrates the problem would be helpful, as would the exact text of the message with any following TRACE lines.
It looks to me like that message comes when you call a module or function and supply a named parameter that the module or function is not expecting.
For instance:
cylinder(xyzzy=3);
WARNING: variable xyzzy not specified as parameter in file , line 1
TRACE: called by 'cylinder' in file , line 1
The TRACE lines should point at the lines causing the problem.
The scripts where the warnings occur are often several hundred lines long, so I tried these as examples, expecting that they would produce warnings:
a=10;
b=20;
translate([b,0,0])
square([a,b]);
module sq()
{
square([x,y]);
}
translate([-b,0,0])
sq(x=10, y=20);
But they only produce the warning:
ERROR: Parser error: syntax error in file , line 8
Execution aborted
Curious in itself, as there is nothing in line 8, but the warnings I had hoped to provoke do not appear. So I need to take a closer look at an existing script that produces warnings to identify how and where they occur and work out a shorter example from that. May take a little time, in the meantime thanks for your response.
--
This email has been checked for viruses by AVG.
https://www.avg.com