12-15-2013, 11:01 PM
Nice layout RT.
*
Well I did a little work on Oliver's adventure today. I had a set of stack variables that weren't working the way I had intended. Turned out it was one variable causing all the trouble. There are two similar variables, SB1 and SB2. In this instance SB1=1 and SB2=2. When Oliver goes into a seating compartment and starts snooping around SB1=1 and SB2=2. However when he is searching the overhead rack a ten year old boy who was asleep on one of the seats wakes up. Now SB1=0 and SB2=2. The kid runs out of the compartment. SB1=1 and SB2=1. This is where things get hairy. The variables look simple enough and they are. Quick Basic (QBasic) would look at the variables and see them for what they are. SB1 and SB2. It looks at the ENTIRE variable and the assignment (that's the # after the '=' sign). However I'm not using Quick Basic. I'm using Applesoft Basic. It looks at part of the variable. The first two characters (SB) then it looks at the assignment. See the problem? SB1 and SB2 have the SAME first two characters. So the computer is looking at SB1 and SB2 but basic is seeing SB and SB. Guess what happens when SB1=1 and SB2=1. Basic sees SB=1 and SB=1. This causes the stack to crash and I get a stack overflow error. However the fix was simple enough. SB1 is still SB1 but SB2 is now SD2 and the stack is working properly. It involved reformatting seventeen line assignments where SB2 was used, about an hours work.
The leg was good to me today. Only some moderate pain but no red spots. Maybe I'll grow some calluses in those areas soon.
Time for me to call it a night. See y'all tomorrow.
![[Image: P1011370-1.jpg]](http://i682.photobucket.com/albums/vv186/Running-Bear/P1011370-1.jpg)
![[Image: P1011286.jpg]](http://i682.photobucket.com/albums/vv186/Running-Bear/P1011286.jpg)
![[Image: DSCN5757.jpg]](http://i292.photobucket.com/albums/mm18/forum-2/DSCN5757.jpg)
*
Well I did a little work on Oliver's adventure today. I had a set of stack variables that weren't working the way I had intended. Turned out it was one variable causing all the trouble. There are two similar variables, SB1 and SB2. In this instance SB1=1 and SB2=2. When Oliver goes into a seating compartment and starts snooping around SB1=1 and SB2=2. However when he is searching the overhead rack a ten year old boy who was asleep on one of the seats wakes up. Now SB1=0 and SB2=2. The kid runs out of the compartment. SB1=1 and SB2=1. This is where things get hairy. The variables look simple enough and they are. Quick Basic (QBasic) would look at the variables and see them for what they are. SB1 and SB2. It looks at the ENTIRE variable and the assignment (that's the # after the '=' sign). However I'm not using Quick Basic. I'm using Applesoft Basic. It looks at part of the variable. The first two characters (SB) then it looks at the assignment. See the problem? SB1 and SB2 have the SAME first two characters. So the computer is looking at SB1 and SB2 but basic is seeing SB and SB. Guess what happens when SB1=1 and SB2=1. Basic sees SB=1 and SB=1. This causes the stack to crash and I get a stack overflow error. However the fix was simple enough. SB1 is still SB1 but SB2 is now SD2 and the stack is working properly. It involved reformatting seventeen line assignments where SB2 was used, about an hours work.
The leg was good to me today. Only some moderate pain but no red spots. Maybe I'll grow some calluses in those areas soon.
Time for me to call it a night. See y'all tomorrow.
15 year veteran fire fighter
Collector of Apple //e's
Beatus homo qui invenit sapientiam
Collector of Apple //e's
Beatus homo qui invenit sapientiam