I was a little confused by your question, so I used a man on gcc to confirm what I thought I knew about -Wall, it is a command that configures warnings...here is the extract from the man page:
-Wall
All of the above -W options combined. This enables
all the warnings about constructions that some users
consider questionable, and that are easy to avoid (or
modify to prevent the warning), even in conjunction
with macros.
So I am curious why you need to use -Wall in conjunction with the headers you mention, is there some sort of academic requirement at work here?
Wayne
If you would like to refer to this comment somewhere else in this project, copy and paste the following link:
I posted a question about apstring.h not working a few months ago, and someone posted a link to a FAQ on dev and apstring.h. It said to put "-Wall C:\Dev-Cpp\include\ap\apstring.cpp" in my command line box so that I could use apstring. Without it, I would get an error message that said "#include needs "filename" or <filename>".
If you would like to refer to this comment somewhere else in this project, copy and paste the following link:
I use the "-Wall" command when I need to use apstring.h, if I wanted to also use apvector or apmatrix, etc, would I need another -Wall command?
not to the best of my knowledge...
Zero Valintine
I was a little confused by your question, so I used a man on gcc to confirm what I thought I knew about -Wall, it is a command that configures warnings...here is the extract from the man page:
-Wall
All of the above -W options combined. This enables
all the warnings about constructions that some users
consider questionable, and that are easy to avoid (or
modify to prevent the warning), even in conjunction
with macros.
So I am curious why you need to use -Wall in conjunction with the headers you mention, is there some sort of academic requirement at work here?
Wayne
I posted a question about apstring.h not working a few months ago, and someone posted a link to a FAQ on dev and apstring.h. It said to put "-Wall C:\Dev-Cpp\include\ap\apstring.cpp" in my command line box so that I could use apstring. Without it, I would get an error message that said "#include needs "filename" or <filename>".
actually i just realized after testing it with and without the -wall command, that i don't need it. but thanks for the help anyways.
-Wall is quite useful, if you want to write tight code, and avoid subtle miscues. It can alos drive you crazy at times.
Wayne
question wayne, since you are already crazy does it not bother you as much? just wondering what i had to look forward to...
:-)
Zero Valintine
Thanks Zero for the laugh!
From all of Us in here.
Wayne (and ...)