| TIP: Click on subject to list as thread! | ANSI |
| echo: | |
|---|---|
| to: | |
| from: | |
| date: | |
| subject: | Re: progress |
-=> Quoting Paul Edwards to All <=- Hello Paul, PE> Hi. I'd like to know whether #including is allowed to PE> drag in the prototype for fprintf or not. No! The printf() family are pretty large. You only need fputs() to implement assert(). To ensure ANSI/ISO compliance, and pick up a few tips from the old hands, you should get "The Standard C Library" by P.J. Plauger. He also gives you permission to use his code beyond mere "fair use". Let me quote him from p.20 regarding assert(). "The macro must not directly call any of the library functions, such as fprintf. Nor may it refer to the macro stderr. These names are properly declared or defined only in the header . The program might not have included that header, and the header must not. A program can define macros that rename any of the names from another header, provided it doesn't include that header. That mandates that the macro call a function with a secret name to do the actual output." PE> Here is the progress of my PD C library: [List deleted] You're doing well! Keep up the good work. Catch you later, Michael Stapleton of Graphic Bits. ... This is your brain. This is your brain on C++. Any questions? --- Blue Wave/RA v2.03 AmyBW [NR]* Origin: The Three Amigas - better than two (3:713/615.0) SEEN-BY: 50/99 54/54 620/243 623/630 624/50 711/409 410 430 807 808 809 932 SEEN-BY: 711/934 712/508 623 713/111 317 601 611 615 618 700 805 888 906 SEEN-BY: 714/906 800/1 @PATH: 713/615 888 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™.