search for: darray

...ndices.push_back(const_int32_172); const_ptr_183_indices.push_back(const_int32_184); const_ptr_183_indices.push_back(const_int64_175); Constant* const_ptr_183 = ConstantExpr::getGetElementPtr(gvar_struct_foo, const_ptr_183_indices); the struct could be struct stest { double age; double darray[3]; } The indices for accessing 'age' would be 0 (32bit) 0 (32bit). For an element of the darray, one however needs 0 (32bit) 1 (32bit) 0-2 (64bit) The same for indices of vectors. The question: Can I at runtime determine (how?) which size I have to use per case? I made some tests...

...nyway because we want to follow the lead of OSX and provide these objects "toll free bridged"... meaning we would implement them using a std c++ library object (e.g. std::basic_string or std::vector) as the first member of the object which will allow us to cast a DString to std::string or DArray to std::vector without any manual or automatic marshaling. As mentioned this is how OSX implements its NS classes, by using the equivalent CF version which again allows casting between the objects. On May 26, 2010, at 6:19 PM, Dale Johannesen wrote: > llvm can output C code, but that target h...

...nyway because we want to follow the lead of OSX and provide these objects "toll free bridged"... meaning we would implement them using a std c++ library object (e.g. std::basic_string or std::vector) as the first member of the object which will allow us to cast a DString to std::string or DArray to std::vector without any manual or automatic marshaling. As mentioned this is how OSX implements its NS classes, by using the equivalent CF version which again allows casting between the objects. >> >> On May 26, 2010, at 6:19 PM, Dale Johannesen wrote: >> >>> llvm ca...

...nyway because we want to follow the lead of OSX and provide these objects "toll free bridged"... meaning we would implement them using a std c++ library object (e.g. std::basic_string or std::vector) as the first member of the object which will allow us to cast a DString to std::string or DArray to std::vector without any manual or automatic marshaling. As mentioned this is how OSX implements its NS classes, by using the equivalent CF version which again allows casting between the objects. This is not how the CFBridge works. Actually, the first member of an object MUST be a pointer to i...

...low > the lead of OSX and provide these objects "toll free bridged"... > meaning we would implement them using a std c++ library object (e.g. > std::basic_string or std::vector) as the first member of the object > which will allow us to cast a DString to std::string or DArray to > std::vector without any manual or automatic marshaling. As mentioned > this is how OSX implements its NS classes, by using the equivalent > CF version which again allows casting between the objects. > > On May 26, 2010, at 6:19 PM, Dale Johannesen wrote: > >> llvm...

...these objects "toll free >>> bridged"... meaning we would implement them using a std c++ >>> library object (e.g. std::basic_string or std::vector) as the >>> first member of the object which will allow us to cast a DString >>> to std::string or DArray to std::vector without any manual or >>> automatic marshaling. As mentioned this is how OSX implements its >>> NS classes, by using the equivalent CF version which again allows >>> casting between the objects. >>> >>> On May 26, 2010, at 6:19 PM, D...

...ouble(matrix(0,ps,ps)), gain=as.integer(F), #48 DUP=T)[c("D","p","f0", "x", "r")] D$d <- d D$eps <- eps D$f0 <- l(model, data, result="pred") - c(output.data(data)) invisible(classed(D,"Darray")) #constructor } -.-.-.-.-.-.-.-.-.-.-.-.-.-.-.-.-.-.-.-.-.-.-.-.-.-.-.-.-.-.-.-.-.-.-.-.-.-.-.- r-devel mailing list -- Read http://www.ci.tuwien.ac.at/~hornik/R/R-FAQ.html Send "info", "help", or "[un]subscribe" (in the "body", not the subject !) T...

...uot;toll free >>>> bridged"... meaning we would implement them using a std c++ >>>> library object (e.g. std::basic_string or std::vector) as the >>>> first member of the object which will allow us to cast a DString >>>> to std::string or DArray to std::vector without any manual or >>>> automatic marshaling. As mentioned this is how OSX implements its >>>> NS classes, by using the equivalent CF version which again allows >>>> casting between the objects. >>>> >>>> On May 26...

...nyway because we want to follow the lead of OSX and provide these objects "toll free bridged"... meaning we would implement them using a std c++ library object (e.g. std::basic_string or std::vector) as the first member of the object which will allow us to cast a DString to std::string or DArray to std::vector without any manual or automatic marshaling. As mentioned this is how OSX implements its NS classes, by using the equivalent CF version which again allows casting between the objects. >>> >>> On May 26, 2010, at 6:19 PM, Dale Johannesen wrote: >>> >>...

llvm can output C code, but that target has bitrotted severely over the last few months and nobody seems to be interested in fixing it. You may need to do some work there. Alternatively you could implement the PPC ABI that you need. There are several examples of supporting multiple ABIs on the same hardware, x86 being the most obvious. A lot of simple stuff will probably Just Work with the

...nyway because we want to follow the lead of OSX and provide these objects "toll free bridged"... meaning we would implement them using a std c++ library object (e.g. std::basic_string or std::vector) as the first member of the object which will allow us to cast a DString to std::string or DArray to std::vector without any manual or automatic marshaling. As mentioned this is how OSX implements its NS classes, by using the equivalent CF version which again allows casting between the objects. >>>> >>>> On May 26, 2010, at 6:19 PM, Dale Johannesen wrote: >>>&g...

We are looking at using Objective-C/C++ in a new game engine.  Objective C's duality of being both very dynamic and very "C" gives us exactly what we need to make the SDK and engineering of games simpler. This means that we will need a way to compile it on all platforms our games will target.  Currently the major platforms we are concerned with include... PC, Mac, XBox 360, PS3,