public inbox for cygwin-xfree@sourceware.org
help / color / mirror / Atom feed
From: jere95 <jeremy120895@yahoo.fr>
To: cygwin-xfree@cygwin.com
Subject: Re: "Erreur" messages when trying to compile
Date: Mon, 18 Feb 2013 15:37:00 -0000 [thread overview]
Message-ID: <1361201816.40559.YahooMailNeo@web171406.mail.ir2.yahoo.com> (raw)
In-Reply-To: <5122464D.8060103@Winfirst.Com>
Thanks a lot I was able to solve the problem!
________________________________
De : Mark Hansen-4 [via Cygwin] <ml-node+s1069669n96269h13@n5.nabble.com>
À : jere95 <jeremy120895@yahoo.fr>
Envoyé le : Lundi 18 février 2013 16h19
Objet : Re: "Erreur" messages when trying to compile
On 2/18/2013 6:42 AM, Jack wrote:
> On 2013.02.18 09:26, jere95 wrote:
>> Hi,
>> I am new to programming and I downloaded cygwin, because I heard it
>> was a
>> good gcc compiler. At the moment I am reading this O'reilly book on
>> C, and I
>> tried compiling the folowing exemple programme out of the book :
>>
>> When I try to compile, this c file, typing : /gcc cards.c -o cards/ ,
>> the
>> cygwin terminal answers :
>>
>>
>>
>> What is the problem?
> For some reason, your examples are not coming through to the mailing
> list.
>
> However, it looks like the messages are very clear. You seem to be
> using "(" (left parenthesis) instead of "{" (left curly brace) on many
> lines. gcc is expecting a closing parenthesis before the next
> semicolon, and it is expecting a semicolon before the next closing
> curly brace.
Yes, here is his example program:
#include<stdio.h>
#include<stdlib.h>
int main()
{
char card_name[ 3];
puts("Enter the card_name: ");
scanf("%2s", card_name);
int val = 0;
if (card_name[0] == 'K') (
val = 10;
} else if (card_name[0] == 'Q') (
val = 10;
} else if (card_name[0] == 'J') (
val = 10;
}else if (card_name[0] == 'A') (
val = 11;
}else (
val = atoi(card_name);
}
printf("The card value is: %i\n", val);
return 0;
}
Look at this line, for example:
if (card_name[0] == 'K') (
My guess is that you typed this in by hand, and didn't see clearly
that the last character should have been an open brace '{' rather
than an open parentheses '('. It looks like you've made the same
error in several other places.
--
Unsubscribe info: http://cygwin.com/ml/#unsubscribe-simple
Problem reports: http://cygwin.com/problems.html
Documentation: http://x.cygwin.com/docs/
FAQ: http://x.cygwin.com/docs/faq/
________________________________
If you reply to this email, your message will be added to the discussion below:http://cygwin.1069669.n5.nabble.com/Erreur-messages-when-trying-to-compile-tp96267p96269.html
To unsubscribe from "Erreur" messages when trying to compile, click here.
NAML
--
View this message in context: http://cygwin.1069669.n5.nabble.com/Erreur-messages-when-trying-to-compile-tp96267p96271.html
Sent from the cygwin-xfree mailing list archive at Nabble.com.
--
Unsubscribe info: http://cygwin.com/ml/#unsubscribe-simple
Problem reports: http://cygwin.com/problems.html
Documentation: http://x.cygwin.com/docs/
FAQ: http://x.cygwin.com/docs/faq/
next prev parent reply other threads:[~2013-02-18 15:37 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2013-02-18 14:26 jere95
2013-02-18 14:43 ` Jack
2013-02-18 15:18 ` Mark Hansen
2013-02-18 15:37 ` jere95 [this message]
2013-02-19 0:46 ` Christopher Faylor
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=1361201816.40559.YahooMailNeo@web171406.mail.ir2.yahoo.com \
--to=jeremy120895@yahoo.fr \
--cc=cygwin-xfree@cygwin.com \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for read-only IMAP folder(s) and NNTP newsgroup(s).