Macro Variable Argument List with __FILE__ and __LINE__

[jake1138]

I couldn't find an example of this anywhere so I post it in the hope
that someone finds it useful. I believe this is compiler specific (I'm
using gcc), as C99 defines __VA_ARGS__. Comments are welcome.

This will print the file name and line number followed by a format
string and a variable number of arguments. The key here is that you
MUST have a space between __LINE__ and the last comma, otherwise
__LINE__ gets eaten by the ## if args is empty. It took me awhile to
figure that out.

#define DEBUGLOG(fmt, args...) printf("%s(%d)" fmt , __FILE__ ,
__LINE__ , ## args)

I'm curious, does anyone know if the equivelant can be done using
__VA_ARGS__?

[Michael Mair]

jake1138 wrote:

I couldn't find an example of this anywhere so I post it in the hope
that someone finds it useful. I believe this is compiler specific (I'm
using gcc), as C99 defines __VA_ARGS__. Comments are welcome.

This will print the file name and line number followed by a format
string and a variable number of arguments. The key here is that you
MUST have a space between __LINE__ and the last comma, otherwise
__LINE__ gets eaten by the ## if args is empty. It took me awhile to
figure that out.

#define DEBUGLOG(fmt, args...) printf("%s(%d)" fmt , __FILE__ ,
__LINE__ , ## args)

I'm curious, does anyone know if the equivelant can be done using
__VA_ARGS__?

I do.
Probably you want to know whether it can be done: Yes, it can be done.

If you want to know how:
#define DEBUGLOG(fmt, ...) \
printf("%s(%d)" fmt, __FILE__, __LINE__, __VA_ARGS__)

(untested)
Cheers
Michael
--
E-Mail: Mine is an /at/ gmx /dot/ de address.

[Chris Torek]

>jake1138 wrote:

This [gcc-specific trick] will print the file name and line number
followed by a format string and a variable number of arguments. ...
[formatting broken originally by google, now fixed:]
#define DEBUGLOG(fmt, args...) \
printf("%s(%d)" fmt , __FILE__ , __LINE__ , ## args)

I'm curious, does anyone know if the equivelant can be done using
__VA_ARGS__?

In article <36************ *@individual.ne t>
Michael Mair <Mi**********@i nvalid.invalid> wrote:I do.
Probably you want to know whether it can be done: Yes, it can be done.

If you want to know how:
#define DEBUGLOG(fmt, ...) \
printf("%s(%d)" fmt, __FILE__, __LINE__, __VA_ARGS__)

(untested)

This is not quite equivalent. GCC's special "prefix ##" syntax
means "remove the preceding pp-token if the variable arguments
are missing". Hence, if one writes:

DEBUGLOG("got here\n");

with the gcc version, one gets:

printf("%s(%d)" "got here", __FILE__, __LINE);

but the C99 version produces:

printf("%s(%d)" "got here", __FILE__, __LINE,);

which is not syntactically valid.

There appears to be no way to achieve the desired effect in C99.
As a workaround, one can write:

#define DEBUGLOG(...) \
(printf("%s(%d) ", __FILE__, __LINE), printf(__VA_ARG S__))

In other words, just use two calls. Or instead of calling printf()
directly, call your own function that takes three-or-more arguments:

extern int debuglog(const char *, int, const char *, ...);
#define DEBUGLOG(...) debuglog(__FILE __, __LINE__, __VA_ARGS__)

In either case, __VA_ARGS__ will necessarily expand to at least one
parameter, so that the "remove preceding pp-token" behavior is never
needed.
--
In-Real-Life: Chris Torek, Wind River Systems
Salt Lake City, UT, USA (40°39.22'N, 111°50.29'W) [phone]
email: forget about it http://web.torek.net/torek/index.html
Reading email is like searching for food in the garbage, thanks to spammers.

[Michael Mair]

Chris Torek wrote:

jake1138 wrote:

This [gcc-specific trick] will print the file name and line number
followed by a format string and a variable number of arguments. ...

[formatting broken originally by google, now fixed:]

#define DEBUGLOG(fmt, args...) \
printf("%s(%d)" fmt , __FILE__ , __LINE__ , ## args)

I'm curious, does anyone know if the equivelant can be done using
__VA_ARGS_ _?

In article <36************ *@individual.ne t>
Michael Mair <Mi**********@i nvalid.invalid> wrote:

I do.
Probably you want to know whether it can be done: Yes, it can be done.

If you want to know how:
#define DEBUGLOG(fmt, ...) \
printf("%s(%d)" fmt, __FILE__, __LINE__, __VA_ARGS__)

(untested)

This is not quite equivalent. GCC's special "prefix ##" syntax
means "remove the preceding pp-token if the variable arguments
are missing". Hence, if one writes:

DEBUGLOG("got here\n");

with the gcc version, one gets:

printf("%s(%d)" "got here", __FILE__, __LINE);

but the C99 version produces:

printf("%s(%d)" "got here", __FILE__, __LINE,);

which is not syntactically valid.

There appears to be no way to achieve the desired effect in C99.
As a workaround, one can write:

#define DEBUGLOG(...) \
(printf("%s(%d) ", __FILE__, __LINE), printf(__VA_ARG S__))

In other words, just use two calls. Or instead of calling printf()
directly, call your own function that takes three-or-more arguments:

extern int debuglog(const char *, int, const char *, ...);
#define DEBUGLOG(...) debuglog(__FILE __, __LINE__, __VA_ARGS__)

In either case, __VA_ARGS__ will necessarily expand to at least one
parameter, so that the "remove preceding pp-token" behavior is never
needed.

Thank you very much!
I never used this gcc extension (-std=cXX -pedantic...), so I was
too quick with my assumptions.
Cheers
Michael
--
E-Mail: Mine is an /at/ gmx /dot/ de address.

[SM Ryan]

"jake1138" <co******@gmail .com> wrote:
# I couldn't find an example of this anywhere so I post it in the hope
# that someone finds it useful. I believe this is compiler specific (I'm
# using gcc), as C99 defines __VA_ARGS__. Comments are welcome.
#
# This will print the file name and line number followed by a format
# string and a variable number of arguments. The key here is that you
# MUST have a space between __LINE__ and the last comma, otherwise
# __LINE__ gets eaten by the ## if args is empty. It took me awhile to
# figure that out.
#
# #define DEBUGLOG(fmt, args...) printf("%s(%d)" fmt , __FILE__ ,
# __LINE__ , ## args)

Alternatively,

debug.h
typedef void (*DebugLogForma t)(char *format,...);
DebugLogFormat debugLogSetup(c har *file,int line);
#define DEBUGLOG (debugLogSetup( __FILE__,__LINE __))
debug.c
static char *file; static int line;
static void debugLogFormat( char *format,...) {
printf("[%s:%d] ",file,line );
va_list list; va_start(list,f ormat);
vprintf(format, list);
va_end(list);
}
DebugLogFormat debugLogSetup(c har *file0,int line0) {
file = file0; line = line0;
return debugLogFormat;
}

--
SM Ryan http://www.rawbw.com/~wyrmwif/
A bunch of savages in this town.

[Dave Thompson]

On Mon, 07 Feb 2005 12:05:08 -0000, SM Ryan
<wy*****@tang o-sierra-oscar-foxtrot-tango.fake.org> wrote:
<snip>

Alternatively,

debug.h
typedef void (*DebugLogForma t)(char *format,...);
DebugLogFormat debugLogSetup(c har *file,int line);
#define DEBUGLOG (debugLogSetup( __FILE__,__LINE __))
debug.c
static char *file; static int line;
static void debugLogFormat( char *format,...) {
printf("[%s:%d] ",file,line );
va_list list; va_start(list,f ormat);
vprintf(format, list);
va_end(list);
}
DebugLogFormat debugLogSetup(c har *file0,int line0) {
file = file0; line = line0;
return debugLogFormat;
}

Not safe for threading, which is not in standard C but is in many C
systems and programs. Why not just

..h
typedef int like_printf (const char * /*restrict*/, ...);
like_printf * logPrefix (const char * file, /*unsigned?*/long line);
#define DEBUGLOG logPrefix(__FIL E__,__LINE__) /*printfargs*/
..c
like_printf * logPrefix (const char * file, long line)
{ printf ("[%s:%ld] ", file, line); return printf; }
or even
static bool logflag = false;
/* some way to set to true -- or viceversa */
static int dont_printf (const char * /*restrict*/ fmt, ...)
{ return 0; }
like_printf * logPrefix (const char * file, /*ditto*/long line)
{ if( !logflag ) return dont_printf;
/*else*/ /*as before*/ }

Note that this evaluates the log-data arguments even if logging is
disabled by the flag; dont_printf is actually called but discards the
values. This may be costly and generally it is bad style to have
needed sideeffects in statements whose apparent purpose is debugging;
OTOH macro schemes that suppress the evaluation need to be tested in
(only?) the release version, or code-reviewed carefully, or both, to
ensure that they don't have such bugs.

- David.Thompson1 at worldnet.att.ne t