search for: long_t

On Sat, 16 Apr 2005 10:38:10 -0500, Chris Lattner wrote: > While I don't think that having 'long_t' or something like that is > necessarily a good idea, I do think that having an 'intptr' type could be > a useful feature, with the advantage of it being a language-independent > construct. I think this would capture what you're really going for, and > have very sim...

...ally appropriate. The problem is that 'long' varies in different ways on different platforms/os's, some of which make sense, and some of which do not. Also, this is a very c-centric request, I am not sure if it makes sense for other people. While I don't think that having 'long_t' or something like that is necessarily a good idea, I do think that having an 'intptr' type could be a useful feature, with the advantage of it being a language-independent construct. I think this would capture what you're really going for, and have very simple and well-defined...

Hello, I was asking some questions on IRC tonight about LLVM and 32bit/64bit compatibility. I'm sure some of these questions sound a bit naive, but so far you guys have been wonderful at forgiving my lack of knowledge :) I'm interested in having one LLVM bytecode file that I can then turn into a 32bit or 64bit ELF file that links against 32bit or 64bit ELF shared libraries, respectively.

...0.1991832405 227 1.116115e+12 2005-05-15 -0.0029508672 228 1.116202e+12 2005-05-16 0.1759385169 229 1.116288e+12 2005-05-17 -0.7524182200 230 1.116374e+12 2005-05-18 0.0271098670 Here is the code wich forms input matrix to make_stars function: transpose_stars = function(lat_b, long_b,lat_t,long_t,step){ matrix <- readSO2Data(lat_b, long_b) // read an arbitrary point for calculating matrix size nlat <- (lat_t-lat_b)/step+1 nlong <- (long_t-long_b)/step+1 ntime <- length(matrix$value) list_lat<-list() list_long<-list() list_time<-list() for( m in 1:nlat){ list_lat[m]&l...