ted@imsvax.UUCP (Ted Holden) (09/27/86)
Does anyone know exactly how TP inline code works, whether it actually sets up an area of machine code which executes as described or whether it's interpreted, or maybe some combination of both? I recently translated an assembler routine which is part of a system for dealing with polyphonic music on PCs into inline code which I know is correct, since I'd rather deal with this particular application in Turbo than C or basic, but the results unfortunately sound like three dogs growling at eachother, which is not what the original routine in basic/masm sounds like and not what Mozart intended. This leads me to believe that inline code is interpreted in some way i.e. that it isn't really fast enough to produce notes higher than dog growls... Ted Holden, IMS
smvorkoetter@watmum.UUCP (Stefan M. Vorkoetter) (10/01/86)
Turbo Pascal inline code is definitely real. I have written lots of software using it to gain speed advantages over straight Turbo Pascal. I have used it for interrupt handling, and real time raster graphics applications. Using debug on the compiled code verifies it. The code is in there exactly as you specify it in the inline statement. You must have translated something wrong. Perhaps, one of your data elements in the inline statement is making a byte where you intended a word, or vice-versa. Or maybe, you have some resident utility running that is stealing a lot of cycles.