| TIP: Click on subject to list as thread! | ANSI |
| echo: | |
|---|---|
| to: | |
| from: | |
| date: | |
| subject: | Re: Conventions? C |
In a message of 25 Sep 94 Roy McNeill wrote to me:
Hi Roy,
RM> Hi Ray
RM> I think I'd find this approach a bit less manageable. If I came back to
RM> the project after a break, and wanted to #include another header file in
RM> routine X, I'd have to hunt down the "master" file and
include it there.
The times I have resorted to this type of approach, the "master"
file has had the name of the completed project or object. The other files
being things like input.c etc. where the support files weren't large enough
to justify being compiled into individual objects, but are too large to
effectively maintain in the same file.
C++ makes life so much easier than to have to make decisions like this anyway...
Regards
Ray
--- Spot 1.3 Unregistered
* Origin: Cutting through the reality... (3:622/401.9)SEEN-BY: 54/54 622/401 407 711/401 407 410 430 436 437 438 439 440 446 807 SEEN-BY: 711/808 809 932 934 942 @PATH: 622/401.9 711/439 430 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™.