Re: Global symbol "$buidTarget" requires explicit package name

That's because you have mis-spelled $buildTarget by omitting the letter l. Using strict has saved your bacon.

Comment on Re: Global symbol "$buidTarget" requires explicit package name Select or Download Code

Replies are listed 'Best First'.
Re^2: Global symbol "$buidTarget" requires explicit package name by Fletch (Bishop) on May 13, 2020 at 17:10 UTC
Don't feel bad because even those of us who've been doing this for ages will still occasionally sit there and blank out despite the error message explicitly telling what's wrong. It's only obvious after you've bothered to show it to someone else. And you read it again. And then sit down and actually read it. And then there's the "Derp." If you ever have a debugging problem like this where you're not seeing the problem, go walk off for 5-10 minutes and do something unrelated. When you come back and look at it fresh it can help. The cake is a lie. The cake is a lie. The cake is a lie.	[reply]
Re^3: Global symbol "$buidTarget" requires explicit package name by BillKSmith (Monsignor) on May 13, 2020 at 19:04 UTC
Another equally strange, but often effective technique is called Rubber_duck_debugging. Bill	[reply]
Re^3: Global symbol "$buidTarget" requires explicit package name by Aaronrp (Scribe) on May 15, 2020 at 02:42 UTC
Back in the '80s when I was using IBM BASICA, I got stuck for three weeks because I typed `F0R X = 1 TO MAX` at the start of a very long line with multiple statements, instead of `FOR X = 1 TO MAX` I do not know when syntax highlighting was invented but it's great stuff.	[reply] [d/l] [select]
Re^2: Global symbol "$buidTarget" requires explicit package name by Anonymous Monk on May 18, 2020 at 05:15 UTC
thank you!	[reply]