Mac would have a fit if he needs to use the library. He hates stuff that is unnecessary!
I tested both of the INTERRUPT and INTERRUPTX procedures by using a new BI file that did not include the DECLARE statements in QB.BI. The new file I made is called RegType.BI as below:
ax AS INTEGER
bx AS INTEGER
cx AS INTEGER
dx AS INTEGER
bp AS INTEGER
si AS INTEGER
di AS INTEGER
flags AS INTEGER
ds AS INTEGER
es AS INTEGER
That is all that is in it! So I included it in my Interrupt and InterruptX programs to see how it worked. In fact I found that I did not even need InterruptX in any program to access DS and ES! Strange eh? Just CALL Interrupt seemed to work fine! I did not DECLARE them in my programs either!
Seems that QB4.5 must define the SUBs in the library somewhere. If the library is included with ALL programs when compiled, there would be some bloating of the EXE file at compile time. This is not necessary in most programs!
My idea would be to either offer an option at compile time or somehow have QB64 figure out if the library is required. That would be up to you Galleon.
It took me a year to realize that you needed the Library with ABSOLUTE or INTERRUPT in a program and newbies just wonder why it doesn't run and gives an error.
Are you planning on using the present library or a new one? It would be better if we don't have to remember to load it.
But then Mac won't be happy either LOL.
Thanks for your time,
|Response Title||Author and Date|
|RE: Having to define Interrupt & InterruptX||on Oct 10|