If and get; really short post, help!

This is my program:

Code:

---

#include <stdio.h>

void main()
{
        char love[20];


        printf("Insert the name of the person that you love. \n");
        gets(love);
       
        if(love == "Lisa")
        {        printf("\n Wonderful, because %s loves you too!", love);
        }
        else if(love == "Alex")
        {        printf("\n Wonderful, because %s loves you too!", love);     
        }
        else
        {        printf("\n Error! \n You do not love %s.", love);
        }
       
}

---

However, when run on Quincy 2000 I receive errors, and my first two "If" statements do not work. Everytime I type in a name, it automatically goes to the third if statement.
Also, my error says something about "the return value for main is not int". But I don't have a return value, nor do I have any integers.

What is the problem?
Thank you.

you have to call the function strcmp() to compare two strings.

Code:

---

if( strcmp(love,"Lisa") == 0)
{
  // the strings are equal
}

---

main needs to return int, not void, that is why you get that error.

You have to understand what is happening in your program and why that won't work.

Code:

---

if(love == "Lisa")

---

The above is NOT how you do string comparisons in C. You need to be using the strcmp function in the <string.h> header. What is happening above is that the program is comparing to see if the address of the love array is equal to the address of the string literal "Lisa". Those two addresses will NEVER be equal. Neither will the address of the love array ever be equal to the string literal "Alex".

Never heard of Quincy 2000 but maybe your code should look like this:

Code:

---

#include <stdio.h>
#include <string.h> //  Needed for stricmp
void main()
{
        char love[20] = {0};
        printf("Insert the name of the person that you love. \n");
        gets(love);
       
        if(stricmp(love,"Lisa") == 0)
        {
        printf("\n Wonderful, because %s loves you too!", love);
        }
        else        if(stricmp(love,"Alex") == 0) 
        {
        printf("\n Wonderful, because %s loves you too!", love);     
        }
        else
        {
        printf("\n Error! \n You do not love %s.", love);
        }
}

---

There is no such standard function as stricmp. And again, main needs to return int, not void.

And never ever use gets(). It's not safe. Use fgets() instead.

Yep, you're right about gets and main return but stricmp is the Win32 version of strcasecmp in the Linux and *nix world.

Been using it for years in all sorts of Win32 projects, hasn't failed me yet.

Bob

Code:

---

#include <stdio.h>
#include <string.h>
int main()
{
        char love[20] = {0};
        printf("Insert the name of the person that you love: \n-> ");
        gets(love);
       
        if(!strcmp(love,"Lisa"))
        {
        printf("\n Wonderful, because %s loves you too!", love);
        }
        else        if(!strcmp(love,"Alex")) 
        {
        printf("\n Wonderful, because %s loves you too!", love);     
        }
        else
        {
        printf("\n Error! \n You do not love %s.", love);
        }
        gets(love);
        return 0;
}

---

As its a int you need to put a return 0; at the end. Also the gets before the return will stop thw window closing before you get to read the ouput.

Ugh! Please don't ever encourage the use of gets(). Did you not read my previous post in this same thread?

Quote:

---

Originally Posted by BobS0327

Yep, you're right about gets and main return but stricmp is the Win32 version of strcasecmp in the Linux and *nix world.

Been using it for years in all sorts of Win32 projects, hasn't failed me yet.

Bob

---

Hence the phrase:

Quote:

---

Originally Posted by cwr

There is no such standard function as stricmp.

---

The standard refers to the ANSI C standard. That is to say the "rules" for the C language itself. Anything that isn't standard is either undefined, or implementation specific. AKA: Not standard.


Quzah.

Ansi C standards bring back fond memories of writing DOS console apps. Being a contract programmer, I just can't remember the last time a potential employer asked me if I was knowledgeable in ANSI C standards. Nowadays, skillset requirements are Windows GUI, COM, DCOM, Graphics/Animation etc. There is now a serious demand developing for C# programmers. And the only C# standard is the Bill Gates standard.

All of the high end stuff C stuff I worked on would never meet ANSI C standards.

The point I'm trying to make is that standards are nice but I wouldn't get in a tither over them.

BTW I have K&R's The C Programming Lanuage. It's been superceded by Petzold on Windows, Russinovich on Windows Internals, Hart on Systems Programming etc.

Bob

we are in the presence of a contract programmer, I am unworthy.

-seriously no sarcasm intended.

Quote:

---

Originally Posted by BobS0327

The point I'm trying to make is that standards are nice but I wouldn't get in a tither over them.

---

The reason we harp on standards so much here, is because we're usually dealing with people who don't understand programming at all, or very well. They don't understand why when they put the line:

Code:

---

if( strcmpi( foo, bar ) )

---

on one computer it compiles, but another it doesn't. Therefore we tell them to use the standard variant. You see?

You know what your compiler has, and you know what you can use. Most people don't. Thus, it is so much easier to teach them how to do things according to the standard, so they know what the language defines, and how it works. Rather than spend hours explaing to many many people why this works here, but not there; why they can use getch some places but not others. And the like.

You want fun? "Hey n00b, you have some of these. Have fun!"

getc
getch
getche
getchar

"They all read a key."
:D


Quzah.

Quote:

---

Originally Posted by quzah

You know what your compiler has, and you know what you can use. Most people don't. Thus, it is so much easier to teach them how to do things according to the standard, so they know what the language defines, and how it works. Rather than spend hours explaing to many many people why this works here, but not there; why they can use getch some places but not others. And the like.

---

And educational institutions are one of the biggest offenders. I can't count the number of times students are required to learn programming with 15-year-old, obsolete compilers such as Tucbo C, then the students can't understand why the functions in conio.h and dos.h don't work with modern 32-bit compilers!

Quote:

---

Originally Posted by BobS0327

Being a contract programmer, I just can't remember the last time a potential employer asked me if I was knowledgeable in ANSI C standards.

---

Interesting. The last time a potential employer asked me if I was knowledgeable in ANSI C standards was during my last job interview. I am now employed with them. One of the reasons I am employed with them is that I was pleased that I would be working for someone who knew and cared about what ANSI C was. Each to their own, though.

Quote:

---

Nowadays, skillset requirements are Windows GUI, COM, DCOM, Graphics/Animation etc. There is now a serious demand developing for C# programmers. And the only C# standard is the Bill Gates standard.

---

This forum is on "C Programming". If it was called "Getting Windows jobs related to C" or something, the above would be vaguely relevant. As for the C# standard, you'll actually find it is standardised by ECMA as Ecma 334.

Have you heard of embedded systems? Have you heard of unix? Linux? It still exists, you know. In the server world, Windows only has a small percentage of the market.

Quote:

---

All of the high end stuff C stuff I worked on would never meet ANSI C standards.

---

I write a lot of C code that is necessarily system dependent, but I try to abstract that away into an opaque interface whenever practical. That way, my program is still in ANSI C, with a set of function calls that wrap system dependent calls. If I want to port my software to another system, I need only change a small portion of the implementation, and the calling code needn't be aware.

Quote:

---

The point I'm trying to make is that standards are nice but I wouldn't get in a tither over them.

---

I would. Again, this is a forum on "C programming". There are separate forums here on "Linux programming" and on "Windows programming", you may have noticed them. There's a reason for that.

People in this forum are working from all sorts of environments, not just Windows. If you assume Windows and give Windows specific code, it is useless to them if they are not using Windows. Also, even if they are using Windows, then they must be informed that it's not part of standard C. One reason for this is that when someone unrelated later issues a search for a certain topic, and finds a thread concerning what they wanted to know, it will be useless to them if the answers are platform specific.

The same applies to unix specific, or any other platform specific code.

Quote:

---

BTW I have K&R's The C Programming Lanuage. It's been superceded by Petzold on Windows, Russinovich on Windows Internals, Hart on Systems Programming etc.

---

Now it becomes quite clear you are either trolling, or extremely ignorant. To give you the benefit the doubt, I'll assume you're trolling but indulge it anyway.

I've been coding in C professionally for 9 years now, and I have never once written a line of code under Windows, so those books don't even remotely apply to me, yet you say they supercede K&R. Strange.

I've heard that Petzold has a good reputation for Windows programming books, I'm sure it a spectacular publication, but it is a guide for a specific platform, and not about how to program in C.