🚀 go-pugleaf

RetroBBS NetNews Server

Inspired by RockSolid Light RIP Retro Guy

Thread View: comp.sys.apple2.gno
4 messages
4 total messages Started by James L. Brookes Tue, 12 Jan 1993 06:17
varargs lib?
#480
Author: James L. Brookes
Date: Tue, 12 Jan 1993 06:17
7 lines
738 bytes
Subject says it all, is there a varargs libary available?  Will there
be one with C 2.0?
-- 
:::::::::::::::::::::::::::::::::::::::::::::::::::::::::::::::::::::::::
|          James Brookes            | Inet: bb252@cleveland.freenet.edu |
|``What, me worry?'' - A. E. Neuman |   jamesb@cscihp.ecst.csuchico.edu |
:::::::::::::::::::::::::::::::::::::::::::::::::::::::::::::::::::::::::
Re: varargs lib?
#482
Author: Jawaid Bazyar
Date: Tue, 12 Jan 1993 07:41
19 lines
1246 bytes
jamesb@ecst.csuchico.edu (James L. Brookes) writes:

>Subject says it all, is there a varargs libary available?  Will there
>be one with C 2.0?

  ANSI C uses the <stdarg.h> header file to define the variable
argument interface.  ORCA/C 1.3 did not include any of vprintf, vsprintf,
or vfprintf; ORCA/C 2.0 does.

  So basically, it's there, you use a different header than BSD, and
you're stuck if you need v*printf (although there is a 3rd party 
vsprintf available, it's pretty useless without the other functions
in the set, too.)

-- 
 Jawaid Bazyar              |   Ask me about the GNO Multitasking Environment
 Procyon, Inc.              |   for the Apple IIgs!   
 bazyar@cs.uiuc.edu         |   P.O Box 620334
 --Apple II Forever!--      |   Littleton, CO 80162-0334   (303) 933-4649
Re: varargs lib?
#483
Author: Chuck D'Antonio
Date: Tue, 12 Jan 1993 18:34
23 lines
1574 bytes
bazyar@teal.csn.org (Jawaid Bazyar) writes:

>  So basically, it's there, you use a different header than BSD, and
>you're stuck if you need v*printf (although there is a 3rd party 
>vsprintf available, it's pretty useless without the other functions
>in the set, too.)

Not exactly stuck, Jawaid . . . it may be kludge, but using the string
that vsprintf produces as the format string for fprintf or printf
makes the 3rd party version work for all three functions.

>-- 
> Jawaid Bazyar              |   Ask me about the GNO Multitasking Environment
> Procyon, Inc.              |   for the Apple IIgs!   
> bazyar@cs.uiuc.edu         |   P.O Box 620334
> --Apple II Forever!--      |   Littleton, CO 80162-0334   (303) 933-4649

Chuck
-- 
-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=- WRBC--91.5 FM -=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-
Chuck D'Antonio			      <>   "Sleep is for lightweights"
internet: cdantoni@abacus.bates.edu   <>                 -- Henry Rollins
-=-=-=-=-=-=-=-=-=-=-=-=-=-=-  Apple II Forever -=-=-=-=-=-=-=-=-=-=-=-=-=-=-
Re: varargs lib?
#484
Author: Jawaid Bazyar
Date: Tue, 12 Jan 1993 23:21
26 lines
1786 bytes
cdantoni@abacus.bates.edu (Chuck D'Antonio) writes:

>bazyar@teal.csn.org (Jawaid Bazyar) writes:

>>  So basically, it's there, you use a different header than BSD, and
>>you're stuck if you need v*printf (although there is a 3rd party 
>>vsprintf available, it's pretty useless without the other functions
>>in the set, too.)

>Not exactly stuck, Jawaid . . . it may be kludge, but using the string
>that vsprintf produces as the format string for fprintf or printf
>makes the 3rd party version work for all three functions.

  Well, okay, agreed, but let me clarify.  With only vsprintf, you have
to either allocate a buffer or make a static buffer; and if you don't
know how long a particular string may be, you might be doing a lot of
extra work that would be unnecessary with the full set.
  vsprintf has saved my butt several times, but I'm glad ORCA/C 2.0
finally has the full set.
  [ Oh.. the one thing that really irked me about the vsprintf lib
    is that no source was included with which to make the other two. ]
-- 
 Jawaid Bazyar              |   Ask me about the GNO Multitasking Environment
 Procyon, Inc.              |   for the Apple IIgs!   
 bazyar@cs.uiuc.edu         |   P.O Box 620334
 --Apple II Forever!--      |   Littleton, CO 80162-0334   (303) 933-4649
Thread Navigation

This is a paginated view of messages in the thread with full content displayed inline.

Messages are displayed in chronological order, with the original post highlighted in green.

Use pagination controls to navigate through all messages in large threads.

Back to All Threads