1. And if your head explodes.....
- Posted by paulk at uniserve.com Mar 07, 2001
- 366 views
------=_NextPart_000_0011_01C0A71E.F60EDAC0 boundary="----=_NextPart_001_0012_01C0A71E.F60EDAC0" ------=_NextPart_001_0012_01C0A71E.F60EDAC0 charset="iso-8859-1" I've hit the 300 line limit again. This is jsut leading to frustration, = so, I'd like off. I've included my program in case anyone wants to = finish it, if not, c'est la vie. ---Thomas And if your head explodes, thunder in your ear...And if there's no room = on the hill.............And if the band your in starts playing different = tunes, I'll see you on the dark side of the Moon..... ---------/\=3D=3D=3D=3D=3D=3D ------=_NextPart_001_0012_01C0A71E.F60EDAC0 charset="iso-8859-1" <!DOCTYPE HTML PUBLIC "-//W3C//DTD HTML 4.0 Transitional//EN"> <HTML><HEAD> <META content=3D"text/html; charset=3Diso-8859-1" = http-equiv=3DContent-Type> <META content=3D"MSHTML 5.00.2614.3500" name=3DGENERATOR> <STYLE></STYLE> </HEAD> <BODY bgColor=3D#ffffff> <DIV><FONT face=3DArial size=3D2>I've hit the 300 line limit again. This = is jsut=20 leading to frustration, so, I'd like off. I've included my program in = case=20 anyone wants to finish it, if not, <EM>c'est la vie.</EM></FONT></DIV> <DIV> </DIV> <DIV><FONT face=3DArial size=3D2><EM>---Thomas</EM></FONT></DIV> <DIV> </DIV> <DIV> </DIV> <DIV> </DIV> <DIV> </DIV> <DIV> </DIV> <DIV><FONT face=3DArial size=3D2><EM>And if your head explodes, thunder = in your=20 ear...And if there's no room on the hill.............And if the band = your in=20 starts playing different tunes, I'll see you on the dark side of the=20 Moon.....</EM></FONT></DIV> <DIV> </DIV> <DIV> </DIV> <DIV><FONT face=3DArial=20 ------=_NextPart_001_0012_01C0A71E.F60EDAC0-- ------=_NextPart_000_0011_01C0A71E.F60EDAC0 name="Sphere.exw"
2. Re: And if your head explodes.....
- Posted by Mark Brown <mabrown at SENET.COM.AU> Mar 08, 2001
- 364 views
Chris wrote.... > I never even use the error reports from EU anyways.. It's much more > accurate and easier to understand if you debug it yourself.. > Your code doesn't work? Add print statements .. systematically of > course.. I agree. For the price I haven't found any language that suits my needs better. I also rarely need the Eu error report and I'm not much of a programmer. Like Chris, I find the best way to debug is to use print statements in my code to trap where the error is happening and where appropriate, to give me DOS window feedback about the state of my program just before it fails. The 300 line limit shouldn't stop you if you *really* can't afford to register. Mark