search for: virgile

...er I was wondering if it might not be easier to just avoid this clash at all by avoiding it in LLVM. Alternatively I could #undef everything right after including Windows.h. On Thu, Aug 29, 2013 at 11:08 AM, Nick Kledzik <kledzik at apple.com> wrote: > > On Aug 28, 2013, at 7:05 PM, Virgile Bello <virgile.bello at gmail.com> > wrote: > > Right now, we have: > In COFF.h: > class COFF { enum MachineTypes { IMAGE_FILE_MACHINE_UNKNOWN = 0x0, > ... }; }; > In windows.h: > #define IMAGE_FILE_MACHINE_UNKNOWN 0 > > * If you first include COFF.h an...

...be preprocessed into COFF:0. * If you first include Windows.h and then COFF.h, COFF.h won't work because it's enum will become: enum MachinTypes { 0 = 0x0 }; On Thu, Aug 29, 2013 at 6:03 AM, Nick Kledzik <kledzik at apple.com> wrote: > > On Aug 27, 2013, at 5:56 PM, Virgile Bello <virgile.bello at gmail.com> > wrote: > > Yes of course I understand it was done on purpose. > It's just that it makes it impossible to include COFF.h and Windows.h side > by side (which probably wasn't necessary until now). > > > I too am in the camp tha...

On Aug 28, 2013, at 7:05 PM, Virgile Bello <virgile.bello at gmail.com> wrote: > Right now, we have: > In COFF.h: > class COFF { enum MachineTypes { IMAGE_FILE_MACHINE_UNKNOWN = 0x0, ... }; }; > In windows.h: > #define IMAGE_FILE_MACHINE_UNKNOWN 0 > > * If you first include COFF.h and then windows...

...e being excluded. Alternately, could you include the lower level windows headers rather than the top level windows.h (e.g #include <winbase.h> but not <windows.h>) [I've never done Windows development, so I'm just stabbing in the dark here] -Nick On Aug 28, 2013, at 7:19 PM, Virgile Bello wrote: > It was happening in a few files using COFF.h in LLDB for the windows branch (Windows.h is required for some typedef over Mutex, thread, socket, etc...). > > As said before, I am currently checking if it could be avoided (probably some refactoring will be needed). However I...

...tely, could you include the lower level windows headers rather than the top level windows.h (e.g #include<winbase.h> but not<windows.h>) > > [I've never done Windows development, so I'm just stabbing in the dark here] > > -Nick > > On Aug 28, 2013, at 7:19 PM, Virgile Bello wrote: > > >> It was happening in a few files using COFF.h in LLDB for the windows branch (Windows.h is required for some typedef over Mutex, thread, socket, etc...). >> >> As said before, I am currently checking if it could be avoided (probably some refactoring wi...

...r <rnk at google.com> wrote: > IMO the fact that it uses the standard names from the COFF documentation > is a feature, not a bug. > > The elf and macho headers in the same directory use the standard > enumeration names, correct? > > > On Tue, Aug 27, 2013 at 5:41 PM, Virgile Bello <virgile.bello at gmail.com>wrote: > >> Hello, >> >> I noticed that if include\llvm\Support is included alongside Windows.h, >> there will be many define conflict leading to compilation errors, such as: >> >> COFF.h (enum): enum MachineTypes { IMAG...

...alternative naming prefix or scheme. Note that if tools depend on COFFDumper::printFileHeaders output, it might still need to print as it was before -- so the easiest choice might be to maybe just drop the IMAGE_ (anyway it's in llvm::COFF so it shouldn't matter). Is it important? Thanks, Virgile -------------- next part -------------- An HTML attachment was scrubbed... URL: <http://lists.llvm.org/pipermail/llvm-dev/attachments/20130828/7ac44c8f/attachment.html>

IMO the fact that it uses the standard names from the COFF documentation is a feature, not a bug. The elf and macho headers in the same directory use the standard enumeration names, correct? On Tue, Aug 27, 2013 at 5:41 PM, Virgile Bello <virgile.bello at gmail.com>wrote: > Hello, > > I noticed that if include\llvm\Support is included alongside Windows.h, > there will be many define conflict leading to compilation errors, such as: > > COFF.h (enum): enum MachineTypes { IMAGE_FILE_MACHINE_UNKNOWN = 0...

On Aug 27, 2013, at 5:56 PM, Virgile Bello <virgile.bello at gmail.com> wrote: > Yes of course I understand it was done on purpose. > It's just that it makes it impossible to include COFF.h and Windows.h side by side (which probably wasn't necessary until now). I too am in the camp that it is a feature to use the...

Hi all, I'm looking for some menu examples for Murali's menu system. Specifically, a headstart on creating a Kickstart menu which covers the most common options with the intention of creating this: label ks.menu kernel vmlinuz.ks.$DIST append ksdevice=eth0 ks=http://kickstartserver/$DIST/Custom/ks.cfg.$DIST initrd=initrd.ks.$DIST lang= devfs=nomount ramdisk_size=8192 Hmm...looking

Dear R users, As a new comer to R, I would like to create a new variable using if statements but don't know how to do it. Basically, I have two variables (EvHint and MinTex). I want to create a third variable called RiskTest. In SPSS, my syntax would look like Compute RiskTest=0. if (EvHint=1 & MinTex=1) RiskTest=1. Question: How do I do this with R? My Data EvHint<-c(0, 0, 0, 1,

Hello, In my LLVM frontend (CLR/MSIL), I am currently using first-class aggregates to represent loaded value types on the "CLR stack". However, I noticed that when calling external method taking those aggregate by value, they were not passed as I expected: %COLORREF = type { i8, i8, i8, i8 } declare i32 @SetLayeredWindowAttributes(i8*, %COLORREF, i8, i32) I call this function with

Hi, Suppose I have a categorical variable called STREET, and I have 30 levels for it (i.e. 30 different streets). I want to find all those streets with only 15 observations or below then collapse them into a level called OTHER. Is there a quick way, other than using a for() loop, to do it? Currently what I'm doing is something like: ### Collapse STREET (those < 15) st <- c()

Hi, I asked some days ago how to guess the o.s. the machine is running. I found that it is stored in a variable called R_PLATFORM. Now I need a full list of all the values this variable can have because I need to set an option depending on the endianness of the platform in which we are compiling the package. Anyone can help me? Thanks, Virgilio Gómez Rubio Dpto. Estadística e

Hi, A new release of RArcInfo is avaialable from CRAN and http://matheron.uv.es/~virgil/Rpackages/RArcInfo/ The changes made are: *V 0.4-2 - 'index' argument added to plotarc to select the arcs to plot. - 'index' argument added to plotpal to select the polygons to plot. - New function 'get.nb', which, given a set of polygons, returns the neighbouring polygons of

Hi, A new release of RArcInfo is out, together with a draft of the tutorial. You can get both from http://matheron.estadi.uv.es/~virgil/Rpackages/RArcInfo Windows binaries are also available and package source can also be downloaded from CRAN. I 'd like to encourage users of the package to read the tutorial and report ideas. Besides, I would like to keep a web page on works where RArcInfo is

Hi, I have just put the source code (and a zip file for Window$ users) of package DCluster in my website: http://matheron.estadi.uv.es/~virgil/Rpackages/DCluster/ DCluster is a package that contains routines for the detection of spatial clusters of diseases (Openshaw's GAM, Besag and Newell, Kulldorff and Nagarwalla, Stone's Test and others). A full description can be found here:

Hi, As Frank M. Howell noticed (and probably other users), the Windows binaries for DCluster I put in my web page are not working... I have compiled the source code again and know it does. Please, download it again, and sorry for the inconvenience. The URL is http://matheron.uv.es/~virgil/Rpackages/DCluster DCluster is a package that implements some methods for the detection of spatial

At least it appears that way on my FreeBSD 8.1 system. This is probably unnoticeable in regular use but I happen to use CFengine(v2) for system configuration & monitoring. If it notices dovecot not running it tries to start it and hangs. I believe cfengine (cfagent) has created a pipe to monitor the start commmand's stderr and is waiting for this pipe to close. This never happens

Hello, As part of a MSIL (i.e. C#) to LLVM frontend I am currently working on ( https://github.com/xen2/SharpLang ), I would need some help/hint about how to properly design "PInvoke callbacks". Through "PInvoke" mechanism .NET allows you to call C functions, i.e.: C#: [DllImport("libc.so")] extern void mempcy(void* dest, void* src, int size); // declaration of C