This commit was manufactured by cvs2svn to create tag 'V1_180'.

git-svn-id: file:///Users/olsen/Code/migration-svn-zu-git/logical-line-staging/clib2/tags/V1_180@14757 87f5fb63-7c3d-0410-a384-fd976d0f7a62

library/amiga.lib_rev.h

@@ -1,6 +1,6 @@
 #define VERSION		1
-#define REVISION	178
+#define REVISION	180
-#define DATE		"7.10.2004"
+#define DATE		"23.10.2004"
-#define VERS		"amiga.lib 1.178"
+#define VERS		"amiga.lib 1.180"
-#define VSTRING		"amiga.lib 1.178 (7.10.2004)\r\n"
+#define VSTRING		"amiga.lib 1.180 (23.10.2004)\r\n"
-#define VERSTAG		"\0$VER: amiga.lib 1.178 (7.10.2004)"
+#define VERSTAG		"\0$VER: amiga.lib 1.180 (23.10.2004)"

library/amiga.lib_rev.rev

@@ -1 +1 @@
-178
+180

library/c.lib_rev.h

@@ -1,6 +1,6 @@
 #define VERSION		1
-#define REVISION	178
+#define REVISION	180
-#define DATE		"7.10.2004"
+#define DATE		"23.10.2004"
-#define VERS		"c.lib 1.178"
+#define VERS		"c.lib 1.180"
-#define VSTRING		"c.lib 1.178 (7.10.2004)\r\n"
+#define VSTRING		"c.lib 1.180 (23.10.2004)\r\n"
-#define VERSTAG		"\0$VER: c.lib 1.178 (7.10.2004)"
+#define VERSTAG		"\0$VER: c.lib 1.180 (23.10.2004)"

library/c.lib_rev.rev

@@ -1 +1 @@
-178
+180

library/changes

@@ -1,3 +1,18 @@
+c.lib 1.180 (23.10.2004)
+
+- The printf() family now produces no output at all for %e, %f and %g if the
+  floating point support code is disabled. Previously, a minimum field width
+  specification could take effect, printing a series of 0 or blank space
+  characters where no output should have been produced.
+
+
+c.lib 1.179 (22.10.2004)
+
+- The scanf() family no longer assumes that a leading '0' indicates that the
+  following digits form an octal number if the conversion type has been
+  specified as already '%x' already.
+
+
 c.lib 1.178 (7.10.2004)
 
 - The OS4 version had floating point math support code enabled in all

library/debug.lib_rev.h

@@ -1,6 +1,6 @@
 #define VERSION		1
-#define REVISION	178
+#define REVISION	180
-#define DATE		"7.10.2004"
+#define DATE		"23.10.2004"
-#define VERS		"debug.lib 1.178"
+#define VERS		"debug.lib 1.180"
-#define VSTRING		"debug.lib 1.178 (7.10.2004)\r\n"
+#define VSTRING		"debug.lib 1.180 (23.10.2004)\r\n"
-#define VERSTAG		"\0$VER: debug.lib 1.178 (7.10.2004)"
+#define VERSTAG		"\0$VER: debug.lib 1.180 (23.10.2004)"

library/debug.lib_rev.rev

@@ -1 +1 @@
-178
+180

library/m.lib_rev.h

@@ -1,6 +1,6 @@
 #define VERSION		1
-#define REVISION	178
+#define REVISION	180
-#define DATE		"7.10.2004"
+#define DATE		"23.10.2004"
-#define VERS		"m.lib 1.178"
+#define VERS		"m.lib 1.180"
-#define VSTRING		"m.lib 1.178 (7.10.2004)\r\n"
+#define VSTRING		"m.lib 1.180 (23.10.2004)\r\n"
-#define VERSTAG		"\0$VER: m.lib 1.178 (7.10.2004)"
+#define VERSTAG		"\0$VER: m.lib 1.180 (23.10.2004)"

library/m.lib_rev.rev

@@ -1 +1 @@
-178
+180

library/m881.lib_rev.h

@@ -1,6 +1,6 @@
 #define VERSION		1
-#define REVISION	178
+#define REVISION	180
-#define DATE		"7.10.2004"
+#define DATE		"23.10.2004"
-#define VERS		"m881.lib 1.178"
+#define VERS		"m881.lib 1.180"
-#define VSTRING		"m881.lib 1.178 (7.10.2004)\r\n"
+#define VSTRING		"m881.lib 1.180 (23.10.2004)\r\n"
-#define VERSTAG		"\0$VER: m881.lib 1.178 (7.10.2004)"
+#define VERSTAG		"\0$VER: m881.lib 1.180 (23.10.2004)"

library/m881.lib_rev.rev

@@ -1 +1 @@
-178
+180

library/net.lib_rev.h

@@ -1,6 +1,6 @@
 #define VERSION		1
-#define REVISION	178
+#define REVISION	180
-#define DATE		"7.10.2004"
+#define DATE		"23.10.2004"
-#define VERS		"net.lib 1.178"
+#define VERS		"net.lib 1.180"
-#define VSTRING		"net.lib 1.178 (7.10.2004)\r\n"
+#define VSTRING		"net.lib 1.180 (23.10.2004)\r\n"
-#define VERSTAG		"\0$VER: net.lib 1.178 (7.10.2004)"
+#define VERSTAG		"\0$VER: net.lib 1.180 (23.10.2004)"

library/net.lib_rev.rev

@@ -1 +1 @@
-178
+180

library/releasenotes

@@ -1,6 +1,10 @@
-c.lib 1.178 (7.10.2004)
+c.lib 1.180 (23.10.2004)
 
-- The OS4 version had floating point math support code enabled in all
+- The printf() family now produces no output at all for floating point
-  libraries and not just "libm.a". Trying to link with, for example,
+  numbers (%e, %f and %g) if the floating point support code is disabled.
-  "libc.a" would bring up a number of unsatisfied symbol references
+  In previous versions of the library some output (series of 0 or blank
-  which could be fixed only by linking against "libm.a", too.
+  space characters) could still be produced.
+
+- The scanf() family no longer ignores a conversion request of
+  type '%x' (hexadecimal) and treats the number to be processed
+  as in octal notation if that number begins with the digit 0.

library/stack.lib_rev.h

@@ -1,6 +1,6 @@
 #define VERSION		1
-#define REVISION	178
+#define REVISION	180
-#define DATE		"7.10.2004"
+#define DATE		"23.10.2004"
-#define VERS		"stack.lib 1.178"
+#define VERS		"stack.lib 1.180"
-#define VSTRING		"stack.lib 1.178 (7.10.2004)\r\n"
+#define VSTRING		"stack.lib 1.180 (23.10.2004)\r\n"
-#define VERSTAG		"\0$VER: stack.lib 1.178 (7.10.2004)"
+#define VERSTAG		"\0$VER: stack.lib 1.180 (23.10.2004)"

library/stack.lib_rev.rev

@@ -1 +1 @@
-178
+180

library/stdio_vfprintf.c

@@ -1,5 +1,5 @@
 /*
- * $Id: stdio_vfprintf.c,v 1.5 2004-09-10 07:39:19 obarthel Exp $
+ * $Id: stdio_vfprintf.c,v 1.6 2004-10-23 16:38:18 obarthel Exp $
  *
  * :ts=4
  *
@@ -979,15 +979,8 @@ vfprintf(FILE * stream,const char * format, va_list arg)
 				else
 					(void)va_arg(arg, double);
 
-				#ifndef NDEBUG
+				minimum_field_width = 0;
-				{
+				format_flags = 0;
-					output_buffer = "*FLOATING POINT NUMBER*";
-					output_len = strlen(output_buffer);
-				}
-				#endif /* NDEBUG */
-
-				CLEAR_FLAG(format_flags,FORMATF_ProduceSign);
-				CLEAR_FLAG(format_flags,FORMATF_ProduceSpace);
 			}
 			#endif /* FLOATING_POINT_SUPPORT */
 		}

library/stdio_vfscanf.c

@@ -1,5 +1,5 @@
 /*
- * $Id: stdio_vfscanf.c,v 1.2 2004-08-08 10:55:57 obarthel Exp $
+ * $Id: stdio_vfscanf.c,v 1.3 2004-10-22 10:57:53 obarthel Exp $
  *
  * :ts=4
  *
@@ -1016,6 +1016,10 @@ __vfscanf(FILE *stream, const char *format, va_list arg)
 				}
 			}
 
+			/* Chose a base according to the conversion to be
+			   expected. For the 'x' and 'i' we examine the
+			   incoming data rather than commit ourselves to
+			   a peculiar data format now. */
 			if(conversion_type == 'd' || conversion_type == 'u')
 				base = 10;
 			else if (conversion_type == 'o')
@@ -1060,7 +1064,11 @@ __vfscanf(FILE *stream, const char *format, va_list arg)
 							 * '0x' prefix or just a zero.
 							 */
 							c = __getc(stream);
-							if (c == 'x' || c == 'X')
+
+							/* This takes care of the '0x' prefix for hexadecimal
+							   numbers ('%x') and also picks the right type of
+							   data for the '%i' type. */
+							if ((c == 'x' || c == 'X') && (conversion_type == 'x' || conversion_type == 'i'))
 							{
 								/* It's the hex prefix. */
 								base = 16;
@@ -1075,7 +1083,7 @@ __vfscanf(FILE *stream, const char *format, va_list arg)
 								if(maximum_field_width > 0)
 									maximum_field_width--;
 							}
-							else if (isdigit(c))
+							else if (isdigit(c) && (conversion_type == 'i')) /* This could be the octal prefix for the '%i' format. */
 							{
 								/* The preceding '0' was part of the
 								   octal prefix. So we don't really know

library/unix.lib_rev.h

@@ -1,6 +1,6 @@
 #define VERSION		1
-#define REVISION	178
+#define REVISION	180
-#define DATE		"7.10.2004"
+#define DATE		"23.10.2004"
-#define VERS		"unix.lib 1.178"
+#define VERS		"unix.lib 1.180"
-#define VSTRING		"unix.lib 1.178 (7.10.2004)\r\n"
+#define VSTRING		"unix.lib 1.180 (23.10.2004)\r\n"
-#define VERSTAG		"\0$VER: unix.lib 1.178 (7.10.2004)"
+#define VERSTAG		"\0$VER: unix.lib 1.180 (23.10.2004)"

library/unix.lib_rev.rev

@@ -1 +1 @@
-178
+180