similar to: Preferred C++ compiler under Windows 2000

> On Mon, 6 Nov 2006, [ISO-8859-2] Žiga Osolin wrote: >> The other thing are the return types. I don't know (it is probably even >> not documented) how VC++ returns smart pointer (boost::smart_ptr), >> or any other type (other basics types, such as int, float, ... are >> probably returned into EAX as with GCC). Once again, we may >> need specific return values

Hello! I have a question how about JIT-ed code and the C++ compiler compatibily. My project (www.baadengine.org) will use llvm and we will provide integration of JIT-ed code directly into C++ code. This means that C++ code can call JIT code just like any other code and JIT-ed code can call C++ code. We will compile to your bytecode from our BSF format. The question is if it is possible this

On Mon, 6 Nov 2006, [ISO-8859-2] Žiga Osolin wrote: > The problem is this is not possible, because what I would compile to JIT > are actual classes. The integration of C++ and JIT code is very > important; for example we would create our own vtbls with JIT-ed code > addresses as the function call target. Ok. Realize that this ties you to a specific compiler version though. >

I'm afraid that still does not completely answer the question. I'll accept that it will work for C programs, given what you quote. It says nothing about C++ however. That's a different animal entirely. g++ mangles names in a completely different fashion than VC++. Does mingw use VC++ style mangling? g++ processes exceptions in a completely different fashion than VC++. I

On Mon, 6 Nov 2006, [ISO-8859-2] Žiga Osolin wrote: > The other thing are the return types. I don't know (it is probably even > not documented) how VC++ returns smart pointer (boost::smart_ptr), > or any other type (other basics types, such as int, float, ... are > probably returned into EAX as with GCC). Once again, we may > need specific return values per arhitecture. It is

Hi. I want to install VC++ on wine, but I am currently doing it on a linux server without GUI, and X11 tunneling doesn't work either. so is there any other way I can install VC++ Runtime files? (I need both 2005 AND 2008)

I'm not sure you understand the problem. Are you saying that a file compiled with mingw can catch an exception thrown by a file compiled with VC++ when the two are linked into a single program? That a program compiled with mingw can be linked against the VC++ runtime and *not* the mingw/gcc runtime? Linking against system DLLs is very different from what I'm talking about. Adam

On Friday 18 February 2005 11:40 am, Jeff Cohen wrote: > I'm not sure you understand the problem. I wouldn't be surprised :) > Are you saying that a file > compiled with mingw can catch an exception thrown by a file compiled > with VC++ when the two are linked into a single program? That a program > compiled with mingw can be linked against the VC++ runtime and *not*

GCC is smart enough to realize it doesn't return. That's because the declaration of abort() is decorated with __attribute__((__noreturn__)). So is GCC smarter than VC++? As it turns out, in VC++ the declaration of abort() is decorated with __declspec(noreturn). Whidbey is not stricter than 2003, it is merely buggier. VC++ has always complained about functions failing to return a

> GCC is smart enough to realize it doesn't return. That's because the > declaration of abort() is decorated with __attribute__((__noreturn__)). > > So is GCC smarter than VC++? As it turns out, in VC++ the declaration of > abort() is decorated with __declspec(noreturn). > > Whidbey is not stricter than 2003, it is merely buggier. VC++ has always > complained

I have searched through the threads and "Rprintf" causing a build error dosen't seem to be a problem for anyone else. And I've read through "R Extensions" and "An Introduction to the .C Interface to R" and there doesn't seem to be any troubleshooting for my problem. My code is straight from "An Introduction to the .C Interface to R" pg. 3. And

Jay Freeman (saurik) wrote: > gcc is correct. According to the ISO specification, the for-init-statement > is supposed to inject any variable names into the same declarative scope as > the condition of an equivalent restructuring of the loop in the form of a > while statement, which in turn fronts the declaration to an extra scope that > surrounds the /entire/ loop construct.

On Thu, Oct 2, 2008 at 11:34 AM, Jay Freeman (saurik) <saurik at saurik.com>wrote: > gcc is correct. According to the ISO specification, the for-init-statement > is supposed to inject any variable names into the same declarative scope as > the condition of an equivalent restructuring of the loop in the form of a > while statement, which in turn fronts the declaration to an extra

Aaron Gray wrote: >> GCC is smart enough to realize it doesn't return. That's because the >> declaration of abort() is decorated with __attribute__((__noreturn__)). >> >> So is GCC smarter than VC++? As it turns out, in VC++ the >> declaration of abort() is decorated with __declspec(noreturn). >> >> Whidbey is not stricter than 2003, it is

gcc is correct. According to the ISO specification, the for-init-statement is supposed to inject any variable names into the same declarative scope as the condition of an equivalent restructuring of the loop in the form of a while statement, which in turn fronts the declaration to an extra scope that surrounds the /entire/ loop construct. VC++ seems to be scoping the variables as if they were

Hi, We have started to use R for our statistical based application especially for Clustering. Clustering is one of features of the software that we are developing. We are developing the entire product using Microsoft Technologies VC++, VB with ODBC. I wanted to use R for performing the Clustering and generate results. I want to call R functions in my C++ program. How can I do that ? I

I would like to utilise the power of R by adding my own software as a package written in C++. As a first step I am trying to write a DLL with a simple function that can be called from R. The DLL contains a C++ routine written and complied in Microsoft Visual C++ Ver 6.0 and is based upon the example in R-Exts eg I am trying to create the following example function SEXP out(SEXP x, SEXP y) {

On Wed, 15 Sep 2004 07:39:23 -0700 Reid Spencer <reid at x10sys.com> wrote: > Yes, in fact I'd be daring enough to suggest that it be the standard. > We'll have fewer compilation problems with VC++ 2005 because it is > (supposedly) more standards compliant than previous versions. Please use > this download: While this may be true, it's not a realistic request. Even

----Original Message Follows---- From: Jeff Cohen <jeffc at jolt-lang.org> Reply-To: jeffc at jolt-lang.org, LLVM Developers Mailing List <llvmdev at cs.uiuc.edu> To: LLVM Developers Mailing List <llvmdev at cs.uiuc.edu> Subject: Re: [LLVMdev] VC++: Cannot open include file: 'windows.h': No suchfile or directory Date: Tue, 21 Dec 2004 16:29:47 -0800

Yes, it should find windows.h with the default configuration. But you have to be suspicious of beta code that Microsoft gives out for free. It might just be very buggy, or it might be deliberately crippled. Considering the price tag on Visual Studio, it's one or the other (and probably both). Out of curiosity, did it accept the solution and project files as is, or did it want to