| TIP: Click on subject to list as thread! | ANSI |
| echo: | |
|---|---|
| to: | |
| from: | |
| date: | |
| subject: | C/c++ Compiler |
DF> NS> JP> EMFBI, but there's a perfectly good DosBeep() method DF> for PM NS> JP> debugging. (-: DF> DF> NS> When I have that problem, I send status messages to the COM DF> port NS> and hook up the laptop over there. Makes it easy to DF> make sure NS> threads are terminating properly. DF> DF> NEIL -- DF> DF> Another alternative (for those who don't have a laptop computer DF> available) is to just use printf() for your status messages. DF> Redirect the output of your PM program to a file. After your DF> program ends, you can use the System Editor to view the contents DF> of the output file. DF> DF> You don't get the instant response as on the laptop, but it's DF> better how would I redirect the printf? I've done fprintf(stderr, "blah) in the past... but sometimes my program would crash and there would be nothing in the file. I wonder... no. I bet it's the Lazywrite feature of the file cache. What do you think? --- Maximus/2 2.01wb* Origin: OS/2 Connection {at} Mira Mesa, CA (1:202/354) SEEN-BY: 12/2442 54/54 620/243 624/50 632/348 640/820 690/660 711/409 413 430 SEEN-BY: 711/807 808 809 934 942 712/353 623 713/888 800/1 @PATH: 202/354 301 1 209/710 209 280/1 396/1 3615/50 229/2 @PATH: 12/2442 711/409 54/54 711/808 809 934 |
|
| SOURCE: echomail via fidonet.ozzmosis.com | |
Email questions or comments to sysop@ipingthereforeiam.com
All parts of this website painstakingly hand-crafted in the U.S.A.!
IPTIA BBS/MUD/Terminal/Game Server List, © 2025 IPTIA Consulting™.