6 hours for a comma, a space, and some caps.....

[boroko]

Hi All,
I was presenting all this primarily show that this kind of thing can really take you for a ride.

Navaidstech: I agree that taking a break gives you new eyes to look at things. It doesn't make up for my ignorance, but it usually helps me.

Chris: Joe S. explained the things that I missed. To amplify, the third was the capitalization of the third INT_HANDLER. As for the interupt technique, it is a macro that is at the heart of DT_INTS. If you haven't used it before, you may want to look at it. I was afraid to use interrupts before I found Darrel Taylor's program that simplifies the whole process. Absolutely wonderful piece of work.

Joe S: I hadn't thought of literally copying the code in like that. That is obvious once you think of it and definitely a "soft forehead" moment.

Those are the kind of thing that I was trying to pull out of the list by starting this. Maybe a thread where people are exposing the traps that they have fell into and the way that they got out of them. A place to go to reduce some of the noise on the list and improve all of our skills. Maybe the effort will keep the list from burning out the major contributors, so we can preserve their attention for the cool stuff.

I hope that someday, when I grow up, one of my posts will become a sticky. Then I will have arrived.....

Bo

[Darrel Taylor]

I hadn't thought of literally copying the code in like that. That is obvious once you think of it and definitely a "soft forehead" moment.

Noooooo .... please don't do that.

That's my biggest pet peeve.
It's an Include module, not a cut&paste snippet.

And as you've already found out, the errors were in your code, not the include file, so it would have accomplished nothing.

Yes, you would have received errors with line numbers referenced to your main program file, but they would not have been any more informative since those lines would still not have pointed to the original problem. And now your main program is filled with stuff that looks like Russian or Chinese (a.k.a. ASM macros). Trying to find errors in your own code only becomes more difficult and confusing.

Then you end up editing something that shouldn't be edited and suddenly nothing works, and I get blamed again.

Put the Include file down and step away from the computer, before you hurt someone.
<br>

[Archangel]

Noooooo .... please don't do that.

That's my biggest pet peeve.
It's an Include module, not a cut&paste snippet.


<br>

I meant it for troubleshooting only Darrel, not to steal your code. Of course the final cut must use it as "licensed" by you, as an include file.

[Darrel Taylor]

I meant it for troubleshooting only Darrel, not to steal your code. Of course the final cut must use it as "licensed" by you, as an include file.

Well, the only "License" is ... Yours to use as you see fit.

So it's just my own personal problem, wish, desire ... peeve.

I seem to be getting more of those, which are Directly proportional to the lack of color in my hair at any given time.
<br>

[Archangel]

Well, the only "License" is ... Yours to use as you see fit.

So it's just my own personal problem, wish, desire ... peeve.

I seem to be getting more of those, which are Directly proportional to the lack of color in my hair at any given time.
<br>

Well Darrel, most of here are Gentlemen / persons. Your generosity has provided us all with talent, most of us do not have, and we are grateful. So the " license " is not to tick you off. Now as for hair color . . . at least you have some ! I encourage everyone to use the code you provided as you prescribed as includes. Copy past should be reserved for troubleshooting only, and the final cut should / must be as includes.

[boroko]

I have thought about it, and listing all of the code in sequence would not have pointed out my problem in this situation. It may have given me some idea of line number, but it would not have helped.

With that in mind, are there any better ways to help see these obscure problems?
The whole point of this thread was to help identify troubleshooting techniques.
In this case, the only thing that helped me was stubbornness and stripping things down until there was nothing left that could be wrong. Then I started adding back sections until the problem reoccurred. Case sensitive searches of the same variables pointed out the caps problem. Nothing brilliant, but things that I hadn't thought to do right away. Oh, that.... and a bunch of luck.

Bo

[Darrel Taylor]

With that in mind, are there any better ways to help see these obscure problems?

With the code from post#1, the first error you would have received would be ...
Found label after column 1. (INT_HANDLER).

That narrows it down to one of 3 lines in the program.
Technically, it points to the exact line, since it was the only one with INT_HANDLER in upper case.
Commenting the lines would have easily shown which one was the problem.

Often, it's not the line numbers in the error that give the best indications, but the (words in brackets) at the right end of the error.
And start from the top of the error list. The first one listed is usually the most important, and resolving that one frequently fixes many of the following errors too.
<br>