Date:	Tue, 22 Aug 2000 15:06:47 +0200
From:	"Eli Zaretskii" <eliz AT is DOT elta DOT co DOT il>
Sender:	halo1 AT zahav DOT net DOT il
To:	amitvikas AT yahoo DOT com
Message-Id:	<3791-Tue22Aug2000150646+0300-eliz@is.elta.co.il>
X-Mailer:	Emacs 20.6 (via feedmail 8.2.emacs20_6 I) and Blat ver 1.8.5b
CC:	djgpp AT delorie DOT com
In-reply-to:	<39A23D42.5E5AC273@yahoo.com> (message from Vikas on Tue, 22 Aug
	2000 14:13:46 +0530)
Subject:	Re: Question.
References:	<Pine DOT LNX DOT 4 DOT 10 DOT 10008220410520 DOT 3559-100000 AT juridico DOT fd DOT uc DOT pt> <1659-Tue22Aug2000093044+0300-eliz AT is DOT elta DOT co DOT il> <39A23D42 DOT 5E5AC273 AT yahoo DOT com>
Reply-To:	djgpp AT delorie DOT com
Errors-To:	nobody AT delorie DOT com
X-Mailing-List:	djgpp AT delorie DOT com
X-Unsubscribes-To:	listserv AT delorie DOT com

> Date: Tue, 22 Aug 2000 14:13:46 +0530
> From: Vikas <amitvikas AT yahoo DOT com>
> 
> Does DJGPP has the same naming convention in C/C++ if __cdecl in not
> defined?

"__cdecl" has no effect with GCC, AFAIK.

There's an __attribute__((cdecl)) thing, but it has a different
spelling and syntax, and is only useful with the -mrtd compiler
option.

I doubt if the original poster had anything like -mrtd in mind.

> c language .o and c++ language .o will not have any problems at link
> time?

Of course, they won't have any problems: every C++ program is using
libc.a, and the absolute majority of libc.a functions are written in
C.

- Raw text -