public inbox for gcc-help@gcc.gnu.org
 help / color / mirror / Atom feed
From: bjorn rohde jensen <shamus@tdcadsl.dk>
Cc: gcc-help@gcc.gnu.org
Subject: Re: Error
Date: Sun, 12 May 2002 09:27:00 -0000	[thread overview]
Message-ID: <3CDE96D3.A5B6AD9D@tdcadsl.dk> (raw)
In-Reply-To: <20020512155016.12434.qmail@webmail10.rediffmail.com>

Hi Rahul,

 g++ is basically telling you, that the function Free is
not declared in your code or any included header files.
The int Free(...) bit, i think, comes from standard C,
where one did not have to prototype functions, but one
could rely on some implicit prototypes. ANSI C made
prototypes a requirement.

Yours sincerely,

Bjorn

Rahul it wrote:
> 
> I am running a Cpp program and when I compile it with g++ it gives
> me some error
> like this
> 
> In function `int main(...)':
> program.cpp: implicit declaration of function `int Free(...)
> 
> I donot know why is this?
> The only way Free() appears in my program is
> Free (str);
> where str type is
> char * str;
> 
> Thanks
> 
> _________________________________________________________
> Click below to visit monsterindia.com and review jobs in India or
> Abroad
> http://monsterindia.rediff.com/jobs

  reply	other threads:[~2002-05-12 16:27 UTC|newest]

Thread overview: 14+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2002-05-12  8:50 Error Rahul  it
2002-05-12  9:27 ` bjorn rohde jensen [this message]
2002-05-12 20:44   ` Error David Dudley
  -- strict thread matches above, loose matches on Subject: below --
2021-11-22  0:45 error Bill Cunningham
2019-11-01  1:44 Error pen1979871192
2007-10-13  1:09 error jay caverte
2007-10-13  1:25 ` error Brian Dessent
2005-04-13 22:39 Error Dean Margell
2001-05-28  3:36 error Torsten Becker
2001-05-28 14:36 ` error Alexandre Oliva
2001-05-28  3:22 error Torsten Becker
2001-02-07  7:57 error Edmond Kereku
2000-01-14 14:03 Error DarkSprrow
2000-04-01  0:00 ` Error DarkSprrow

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=3CDE96D3.A5B6AD9D@tdcadsl.dk \
    --to=shamus@tdcadsl.dk \
    --cc=gcc-help@gcc.gnu.org \
    /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).