"wcfray" wrote:
Got it. <stopped>worrying</stopped> P.S. NOW I know what the GC stands for, and it is apparently not General Compiler?
Right. It ain't MajGen. Failure either
🙂 It's just the "lowly" janitor that cleans the office and you may hear them grumbling that we throw too much trash on the floor instead of the trash cans. Make no mistake, GC's role is important and makes our lives easier - instead of say "C/C++ Corp" offices where everybody at all times should use the recycling bin (or else after a few days they'd run out of office space and halt). It also makes sense to review the code if GC has to spend too much time cleaning said "orphans". But a few droppings... meh.
(which i can tell since you don't know where it comes from 🙂 )
True, but a previously referenced post (from an ostensibly more knowledgeable forum member) also complained that the error message does not tell you where the error was found. I could probably be accurately described as script kiddie, as I am using modified scripts from Roku. I admit that slogging through the sdkdocs can be overwhelming to me. I do try though, and will continue to do so. Since I have not written my own scripts, then is it not reasonable to presume that those errors might be coming from those ever so slightly modified, but canned scripts?
No worries, that was not critique of you but just an observation. Was pointing out it was not something you planned/intended, like "i won't check for invalid here because i know FOR EACH will skip on invalid" - or you would have known
where you made such decision. You likely inherited the not-checking-for-invalid-after-using-some-roXML-API from some example script, sure.
Now regarding why
Warning messages like this cannot show the source line#, see RokuKC's "but not as easy as you might think." I can extrapolate (speculate) on that, probably the VM handles a proper
Error with a C++ `throw` that un-winds the stack and when `catch`-ed upstream, the source script context (incl. line#) is available - but when down-in-the-trenches printing a "not-fatal error" (aka
Warning) like this and continuing execution, line# is not known.
Note: No disrespect of any kind is meant in anything I have to say. If you took my meaning in the worst possible way, then you took my meaning all wrong. No undercurrent either. I have been impressed with the tone of this forum and I hope to be able to continue to participate and learn. I try to use emoticons sparingly because even they can be misconstrued.
Mmm? I am confused here. I had no issue with anything you have said, the point i was trying to make was that if i were to worry about something, orphan instances would me buch further down my list than "FOR EACH var IN invalid" cases. And on top of the list will be "the channel working", of course
😄Indeed, we have a helpful micro-community here. It is the sole source of help outside of the incomplete in parts SDK documentation.
Off-the-cuff, i would like to pay tribute to the following people whose posts over the years have helped me:
- RokuMarkn
- TheEndless
- RokuJoel
- greubel
- RokuChris
- RokuKC
- squirreltown
- destruk
- renojim
- belltown
- gonzotek
Thank you!
