search for: _using_

...nix (so what does it do on cygwin or mingw?). The > portability warnings are still useful, but it does mean that "long" must > be banished from the code. I'm not trying to eliminate the warnings when compiling LLVM -- I'm trying to eliminate the warnings in applications _using_ LLVM which might be (as in our case) using the 64-bit portability mode. So I only want to patch some very commonly included header files in order to compile our application cleanly. I am absolutely not suggesting to banish "long" from the code. m.

...t;> on cygwin or mingw?). The portability warnings are still useful, but >> it does mean that "long" must be banished from the code. > > > I'm not trying to eliminate the warnings when compiling LLVM -- I'm > trying to eliminate the warnings in applications _using_ LLVM which > might be (as in our case) using the 64-bit portability mode. So I only > want to patch some very commonly included header files in order to > compile our application cleanly. I am absolutely not suggesting to > banish "long" from the code. > > m. Didn...

Dear R community, Since upgrading to R v.2.6.1 and re-installing package Hmisc (binary for Mac OS X v.3.4-3), I have been getting a error when trying to make xYplots: >plotcv<-c(34.88, 41.51, 45.81, 51.05, 51.66) >plotcv.se<-c(2.406551, 3.071291, 4.331407, 3.213873, 4.838150) >month<-c(6, 7, 8, 9, 10) >library(Hmisc) >xYplot(Cbind(plotcv, plotcv + plotcv.se,

VS has a 64-bit portability mode, where it will complain when it sees non-portable code. I haven't tried it yet on LLVM, but in my experience it will generate a *lot* of warnings. Every time a size_t or ptrdiff_t is assigned to an int or even a long it will complain (Microsoft defines long as 32-bits, even in win64). On the other hand, gcc defines long as 64-bits on 64-bit Unix (so

...to shoot up immensely _very_soon_, as soon as "multimarkdown composer" hits the app store... none of you has shown that you understand the immensity of having an on-the-fly display while a person is writing... (i knew it'd be important, so i programmed it for myself, but it was only _using_ it that i learned it was _immense_. so my saying that you don't understand it isn't an insult.) and -- even aside from "composer" -- multimarkdown has "marked" doing promotional work for it via any text-editor. what this means is that fletcher has absolutely no incenti...

A while back I promised to provide some feedback on useful extensions to LLVM to better support source language writers (i.e. those _using_ LLVM, not developing it). Below is a list of the ideas I've come up with so far. As I get more of XPL's compiler done, I'll start diving into each of the these areas. I'm posting early in the hopes that discussion will bear some fruit. In discussing these things, I'm mostly i...

Hi, When writing a Rails app, what common tasks can likely result in performance issues? The one I''m aware of is something like: Model.find(:all).each do |elem| # do stuff end Especially when there''s lots of elements in the Model. What other ones are there? Also, does Rails do caching of queries? If I''m in a view and I do: <% if user.admin? %> ... and

On Tue, 6 Jan 2004, Reid Spencer wrote: > A while back I promised to provide some feedback on useful extensions to > LLVM to better support source language writers (i.e. those _using_ LLVM, > not developing it). Below is a list of the ideas I've come up with so > far. Cool! Ideas are alway welcome! > If you respond to this, please respond to each item in a separate > message to the list. That way we can keep track of different topics on > different discuss...

Hi, here are some minor patches that for various reasons I've not submitted yet - I'm just trying to clear my list of differences before christmas... First of all the clear.patch file contains a patch that enables the JIT to drop all global mappings. I need this because when I have N threads I compile N different versions of my functions using different memory areas for global