| TIP: Click on subject to list as thread! | ANSI |
| echo: | |
|---|---|
| to: | |
| from: | |
| date: | |
| subject: | OS/2 4.0 |
Hi, Paul.
PE> PE> FM> As Paul said to you "//" is C++ not Borland.
And you could still
PE> use
PE> PE> FM> "/*...*/" as a one-line comment, as you to
with "{...}" in Pascal.
PE> But
PE> PE> FM> it's the nestability thing which is such a big
advantage. I comment
PE> my
PE> PE> FM> code a lot, with {}, and it's just so easy while debugging to
PE> surround
PE> PE> FM> some bits you don't want to use in that test with (*...*).
PE> PE> In C, you use #if 0, #endif to mask out large blocks of code. BFN.
PE> Paul.
PE> FM> OK, that wouldn't be too much trouble and achieve the desired result.
PE> FM> You could {$define test1} {$ifdef test1} ... {$endif} in Pascal too,
PE> but
PE> FM> (* ... *) is easier.
PE> Some compilers have extensions that allow nested comments, but it's not
PE> standard. BFN. Paul.
Which wouldn't matter in the circumstances where I use it, ie in testing
and debugging. You'd remove that code (or at least the comments around
it) before your prog was "released".
Regards, fIM.
* * Some people think asphalt is a rectal disorder.
@EOT:
---
* Origin: Pedants Inc. (3:711/934.24)SEEN-BY: 711/934 712/610 @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™.