Re: runtime error not caught by compilation check???

Thanks to all who took their time to try to help; especially since my OP does NOT provide an SSCCE nor all the other info that would be helpful. So...

Replying to the questions above in the order they were asked.:

LanX: Execution and error names not match?
ww: I have no clue but assure you, that's exactly what's happening. FWIW, there has not been a file with the name in the error on my machine since shortly after it was created and failed. (Yeah, I know, I should use some sort of version control. Bad on me!)
LanX: shebang....
ww: For all practical purposes, windoze ignores that shebang, but ultimately, execution will be on a Linux box (Apache).
LanX: try....
ww: Good thought, but basicly, I couldn't do that. see first ww reply.
beech: use code on PM site? (1)& (3) "$select" error
ww: Great idea, but failed because I'd removed too much code in effort to be (most of) SSCCEE.
However, after downloading the PM code and restoring what I'd removed, I found a what I think was one problem; the quoting at what became line 50 was INCORRECT. It used single quotes inside the curlies, rather than escaped double quotes.
beech: 2: vers?
ww: 5.24, ActiveState, on dev box, Win7 pro (which harbors an evil spirit of some sort; see first reply to LanX.)
Marshal: (as ww understands question) re "invalid statement before the skedhash assignment"
ww: Some fields in the db are null; I got tired of double checking which were generating the warnings.
And if the discomfort is about the %skedhash = @_, the sub is being passed a hash, %skedrow.

I hope I've also learned something else: Don't post a question at near-midnite, Christmas nite (or any other nite). Sleep on it! I suspect (suspect!) I have now solved the actual-misleading-weird-messages-issues with your help and a variant of the teddy-bear method. Again, thanks, and when I'm confident of the solutions, I'll update with (too much) actual, working code

++$anecdote ne $data

check Ln42!

Comment on Re: runtime error not caught by compilation check??? Select or Download Code

Replies are listed 'Best First'.
Re^2: runtime error not caught by compilation check??? by LanX (Saint) on Dec 26, 2016 at 14:55 UTC
> ww: For all practical purposes, windoze ignores that shebang, but ultimately, execution will be on a Linux box (Apache). IIRC there are various methods on Win to associate script-files to a executable (and none is default) ... > ww: 5.24, ActiveState, on dev box, Win7 pro ... so probably you should check if you have multiple Perl installations on your machine. Try to run the code directly with the same perl.exe which was used for the syntax check and see if the errors still differ. update Probably you want to prepend this to your script `BEGIN { warn "Exe:$^X , Ver:$^V , File:$0" }` [download] and compare the outcome in your different runs. See `perlvar` for details Cheers Rolf _{(addicted to the Perl Programming Language and ☆☆☆☆ :) Je suis Charlie!}	[reply] [d/l]

Replies are listed 'Best First'.

Re^2: runtime error not caught by compilation check???
by LanX (Saint) on Dec 26, 2016 at 14:55 UTC

> ww: For all practical purposes, windoze ignores that shebang, but ultimately, execution will be on a Linux box (Apache).

IIRC there are various methods on Win to associate script-files to a executable (and none is default) ...

> ww: 5.24, ActiveState, on dev box, Win7 pro

... so probably you should check if you have multiple Perl installations on your machine.

Try to run the code directly with the same perl.exe which was used for the syntax check and see if the errors still differ.

update

Probably you want to prepend this to your script

BEGIN { warn "Exe:$^X , Ver:$^V , File:$0" }
[download]

and compare the outcome in your different runs.

See perlvar for details

Cheers Rolf
_{(addicted to the Perl Programming Language and ☆☆☆☆ :)

Je suis Charlie!}

[reply]
[d/l]