Mercurial > hg > xemacs-beta

comparison src/doprnt.c @ 50:ee648375d8d6 r19-16b91

Find changesets by keywords (author, files, the commit message), revision number or hash, or revset expression.
Import from CVS: tag r19-16b91
author cvs
date Mon, 13 Aug 2007 08:56:41 +0200
parents 0293115a14e9
children 8b0bdfdf0cf0
comparison
equal deleted inserted replaced
49:b46643e427ac 50:ee648375d8d6
443 Bytecount string_len; 443 Bytecount string_len;
444 444
445 if (!largs) 445 if (!largs)
446 { 446 {
447 string = Dynarr_at (args, spec->argnum - 1).bp; 447 string = Dynarr_at (args, spec->argnum - 1).bp;
448 /* error() can be called with null string arguments.
449 E.g., in fileio.c, the return value of strerror()
450 is never checked. We'll print (null), like some
451 printf implementations do. Would it be better (and safe)
452 to signal an error instead? Or should we just use the
453 empty string? -dkindred@cs.cmu.edu 8/1997
454 */
455 if (!string)
456 string = "(null)";
448 string_len = strlen ((char *) string); 457 string_len = strlen ((char *) string);
449 } 458 }
450 else 459 else
451 { 460 {
452 Lisp_Object obj = largs[spec->argnum - 1]; 461 Lisp_Object obj = largs[spec->argnum - 1];