| TIP: Click on subject to list as thread! | ANSI |
| echo: | |
|---|---|
| to: | |
| from: | |
| date: | |
| subject: | try |
PM>> The problem here is the lack of consistency. In some places you have to PM>> use 'if (ALLOK)' and in other 'TRY(...)'. PE> The previous way involved doing that too??? Did it? I don't remember that far back! PE> Anyway, you have to be careful with this way, because the test is BEFORE, PE> not after, so if you think you won't bother putting in the last test (for PE> func4()), because it won't fail anyway, then you'll screw up! I hadn't noticed that actually. Certainly a bit of a short comming. PE> I was thinking of the possibility of having a TRYB and TRYA, for test PE> before and test after. The test after will involve doing a break, so it PE> goes back to the previous way of doing it. The above method means you PE> have to check everything. If you want to get lazy, then you have to do PE> an: I think you'd be better off trying to find some of the C implementations of exception handling. Even if you can't find a PD one, you'll at least get some ideas. Now that you're a Unix person, you show be able to find something kicking around Internet. Paul --- GoldED/2 2.42.G1114* Origin: It's life Jim, but not as we know it (3:711/934.1) SEEN-BY: 635/514 640/305 711/809 934 @PATH: 711/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™.