TIP: Click on subject to list as thread! ANSI
echo: cis.tandy.coco
to: Kevin Darling (UG Pres) 76703,4227 (X)
from: James Jones 76257,562
date: 1990-05-03 21:08:54
subject: #3245-C arrays

#: 3254 S10/Tandy CoCo
    03-May-90  21:08:54
Sb: #3245-C arrays
Fm: James Jones 76257,562
To: Kevin Darling (UG Pres) 76703,4227 (X)

Yes, but that's not the same thing.  If you look at the fine print on
varargs.h, or whatever it is, you'll see that the programmer is expected to be
able to claim to know the type he wants to pretend the "next" argument passed
is, so that the compiler need not generate code that actually indicates
anything about the number, type, or size of actual parameters.  (Nothing in the
standard prohibits it, but I doubt that one will find anything save the better
C interpreters that actually do.)

The intent of va_arglist et al. is that there be some extralinguistic way to
think one knows what the types of the arguments are, e.g. by scanning a
printf() format string.

SOURCE: compuserve via textfiles.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™.