CompuServe Thread

Forum unknown · Programming

#Lattice –> Aztec

7 messages in this thread
#31601From: RICH MEDVEDAug 31, 1986 2:21 PM
functions.h was included in the file. I also tried compliling with +L switch to force long ints. In one instance, using Read() and Write() for console IO, everything flowed until the first write was encounted. At that time, the string was written to the CRT but didn't stop at the null. Screen IO continued until I forced an abort. The second attempt was when I wrote the code under Aztec and tried writing to PAR: with Write(). Nothing happened. To debug, I added a printf() before and one after the Write(). The first printf() worked, the second didn't, yet the program terminated as though everything was OK. I've tried #include<functions.h>, compiling with cc +l filname, linking with both ln filname -lc and ln filname -lc32. Makes no difference – program runs, but no printer output. Took the second code, compiled under Lattice, and everything ran (The first originally was compiled under Lattice).
#31683From: Aegis DevelopmentSep 1, 1986 1:22 AM
Did you do someting like … Handle foo; BCPL expects pointers to be on 4 byte boundaries, you should Alloc BCPL structures…
#31716From: RICH MEDVEDSep 1, 1986 1:37 PM
That looks interesting!! I think that may be my problem. Thanks.
#31718From: Aegis DevelopmentSep 1, 1986 1:53 PM
B(etter) C(heck) P(ointers) to L(ongs).
#31718From: Aegis DevelopmentSep 1, 1986 1:53 PM
B(etter) C(heck) P(ointers) to L(ongs).
#31716From: RICH MEDVEDSep 1, 1986 1:37 PM
That looks interesting!! I think that may be my problem. Thanks.
#31683From: Aegis DevelopmentSep 1, 1986 1:22 AM
Did you do someting like … Handle foo; BCPL expects pointers to be on 4 byte boundaries, you should Alloc BCPL structures…