SF.net SVN: frontierkernel: [1180] Frontier/trunk/Common/source

[<and...@us...>]

Revision: 1180
Author:   andreradke
Date:     2006-04-01 08:11:40 -0800 (Sat, 01 Apr 2006)
ViewCVS:  http://svn.sourceforge.net/frontierkernel/?rev=1180&view=rev

Log Message:
-----------
Removed function definitions from langparser.c and langparser.y which conflicted with definitions from the standard C library headers. This fixes a GCC 4.0 compilation error.

Modified Paths:
--------------
    Frontier/trunk/Common/source/langparser.c
    Frontier/trunk/Common/source/langparser.y
Modified: Frontier/trunk/Common/source/langparser.c
===================================================================
--- Frontier/trunk/Common/source/langparser.c	2006-04-01 15:50:59 UTC (rev 1179)
+++ Frontier/trunk/Common/source/langparser.c	2006-04-01 16:11:40 UTC (rev 1180)
@@ -54,7 +54,15 @@
 
 
 //static FILE __file[1];
+/*
+	2006-04-01 kw & aradke: The following static function templates caused
+		a compilation error with GCC 4.0 because we already picked up the
+		functions from stdio.h and string.h via osincludes.h and frontier.h.
+		Therefore, we commented out the following templates. The functions
+		are never called in real life anyway because yytflag is never non-nil.
+*/
 
+/*
 static int fprintf (FILE *f, const char *s, ...) {return (0);}
 
 static FILE *fopen (const char *s1, const char *s2) {return (NULL);}
@@ -62,8 +70,8 @@
 static int fclose (FILE *f) {return (0);}
 
 static int strcmp (const char * str1, const char * str2) {return (0);}
+*/
 
-
 /*
 10/2/91 dmb: a disturbing discovery -- our error handling doesn't deallocate 
 any of the code tree that's been built so for.  searching through langparser.c, 

Modified: Frontier/trunk/Common/source/langparser.y
===================================================================
--- Frontier/trunk/Common/source/langparser.y	2006-04-01 15:50:59 UTC (rev 1179)
+++ Frontier/trunk/Common/source/langparser.y	2006-04-01 16:11:40 UTC (rev 1180)
@@ -59,6 +59,15 @@
 
 //static FILE __file[1];
 
+/*
+	2006-04-01 kw & aradke: The following static function templates caused
+		a compilation error with GCC 4.0 because we already picked up the
+		functions from stdio.h and string.h via osincludes.h and frontier.h.
+		Therefore, we commented out the following templates. The functions
+		are never called in real life anyway because yytflag is never non-nil.
+*/
+
+/*
 static int fprintf (FILE *f, const char *s, ...) {return (0);}
 
 static FILE *fopen (const char *s1, const char *s2) {return (NULL);}
@@ -66,6 +75,7 @@
 static int fclose (FILE *f) {return (0);}
 
 static int strcmp (const char * str1, const char * str2) {return (0);}
+*/
 
 /*
 10/2/91 dmb: a disturbing discovery -- our error handling doesn't deallocate 


This was sent by the SourceForge.net collaborative development platform, the world's largest Open Source development site.