From: "Rafal 'Raf256' Maj" Newsgroups: comp.os.msdos.djgpp Subject: Re: version ? Date: 27 Oct 2002 16:32:36 GMT Organization: news.onet.pl Lines: 55 Sender: raf256 AT poczta DOT onet DOT pl@rafal.joint.eu.org Message-ID: References: NNTP-Posting-Host: rafal.joint.eu.org Mime-Version: 1.0 Content-Type: text/plain; charset=ISO-8859-2 Content-Transfer-Encoding: 8bit X-Trace: news.onet.pl 1035736356 1207 62.233.182.161 (27 Oct 2002 16:32:36 GMT) X-Complaints-To: abuse AT onet DOT pl NNTP-Posting-Date: 27 Oct 2002 16:32:36 GMT User-Agent: Xnews/5.04.25 To: djgpp AT delorie DOT com DJ-Gateway: from newsgroup comp.os.msdos.djgpp Reply-To: djgpp AT delorie DOT com Eli Zaretskii wrote in news:Pine DOT SUN DOT 3 DOT 91 DOT 1021027161818 DOT 3459A-100000 AT is >> I know about __GNUC__, __DJGPP__, are there more informations like >> this ? > __DJGPP_MINOR__ might also be of interest. > What other info are you interested in? Is it only versions of various > tools or something else? Currenlty - only version informations to be included to my programs. Some guestions that I encounter reading docs : `__USING_SJLJ_EXCEPTIONS__' This macro is defined, with value 1, if the compiler uses the old mechanism based on `setjmp' and `longjmp' for exception handling. what - is the new mechanism ? Another approach is to use the predefined macros to calculate a single number, then compare that against a threshold: #define GCC_VERSION (__GNUC__ * 10000 \ + __GNUC_MINOR__ * 100 \ + __GNUC_PATCHLEVEL__) ... /* Test for GCC > 3.2.0 */ #if GCC_VERSION > 30200 GNUC ver. i s stored in 'float' version, like : 3.00.00 after big path: 3.00.50 after small path : 3.00.51 OR : 3.0.0 patch 3.0.1 path 3.0.2 etc ? -- Rafał 'Raf256' Maj http://www.raf256.com