Re: Comet32.444 discrepancy


[ Follow Ups ] [ Post Followup ] [ Signature.net Forum ]

Posted by Grant Foraker on July 20, 2011 at 10:31:55:

In Reply to: Re: Comet32.444 discrepancy posted by Jim Guerber on July 19, 2011 at 08:17:06:

Jim:

I had to debug your program a little to get 700 in, 700 out. Primarily the size of XACCNUM1 should have been 16.0.

LENGTH 1.0 & LOCAL ERR !***
LENGTH 3 & LOCAL BEGIN$ !***
length 3.0 & local work
LENGTH 254 & LOCAL STRACC$
LENGTH 16.0 & LOCAL XACC000F
LENGTH 16.8 & LOCAL XACCNUM0
LENGTH 16.0 & LOCAL XACCNUM1 !***
clear
print(et)

begin$ = '700'
PRINT 'START ';BEGIN$
1025
XACCNUM0 = NUM(BEGIN$,ERR)
print xaccnum0;'xaccnum0'
XACC000F = INT(XACCNUM0) * 100000000
print XACC000F;'XACC000F'
!!!!!XACCNUM1 = XACCNUM0 * 100000000
print XACCNUM1;'XACCNUM1'
!!!!!XACC000F = XACC000F + XACCNUM1
print XACC000F;'XACC000F'
XACC000F = XACC000F * .00000001
print XACC000F;'XACC000F'
WORK = XACC000F
XACC000F = ERR
XACC000F = (XACC000F - 1)
IF XACC000F NE 0 GOTO 1030
print 'error' & goto done
1030
STRACC$ = STR(WORK)
BEGIN$ = STRACC$
1035
PRINT 'END ';begin$;work

done:
wait
stop

excp:
print 'got excp';excp
wait
stop

What I found was the REMing out the two lines with XACCNUM1 does the trick. Compiled in Comet16 the results are correct run under Comet16 or Comet32. Compiled under Comet32 is also good.

I'm going to search for XACCNUM1 and REM out those lines. Maybe the XACCNUM1 has some purpose if the INPUT field contains a decimal (ie 123.45).


Follow Ups:



Post a Followup

Name:
E-Mail:

Subject:

What is the name of the main Signature System's Product?  

Comments:

Optional Link URL:
Link Title:
Optional Image URL:

You may attach up to 5 files to your followup (see below):





Each file can be a maximum of 1MB in length Uploaded files will be purged from the server on a regular basis.


[ Follow Ups ] [ Post Followup ] [ Signature.net Forum ]