search for: dfoo

...9;ve got a list L <- list(L1 = list (foo = "bar" , SL = NULL ) , L2 = list ( foo = "bar" , SL = list (SSL1 = list (DF = data.frame(val = 21, foo = "bar") , DFOO = list(foo = "foo", bar = "bar") ) , SSL2 = list (DF = data.frame(val = 22, foo = "bar") , DFOO = list(foo = "foo", bar = "bar") ) ) ) , L3 = list...

...t; foo <- gsub(",","*",toString(paste('(p',1:3,'*x + > (1-p',1:3,'))',sep=""))) > foo [1] "(p1*x + (1-p1))* (p2*x + (1-p2))* (p3*x + (1-p3))" But now, how can I take derivative of this expression w.r.t. "x"? > dfoo <- D(foo,"x") #doesn't work as well as > dfoo <- D(as.expression(foo),"x") May be there are other ways to handle this kind of situation? Best regards, Oleksandr

...re used to try to minimize the build effort and more importantly speed up builds. Build acceleration tools commonly use the build options, and among them macros, to determine if the output from a build is equivalent or not with a later build of the same compilation unit. The commands ... $ clang -DFOO example.c .. and ... $ clang -DBAR example.c ... produce 100% identical output, since neither macro FOO nor BAR affect the compilation unit. However, the build acceleration tools that do not run the preprocessor will not detect that the input to the compilation stage is identical and so will tre...

...llow for unrecognised macros to just be treated as part of the input string. This means we don't have to worry about complexities like escaping "[[" etc. In the (unlikely) event that somebody's YAML needs to include the literal "[[FOO]]", they simply should not also use -DFOO - use a different name instead, e.g. -DBAR. On Mon, 3 Feb 2020 at 22:04, Fangrui Song <maskray at google.com<mailto:maskray at google.com>> wrote: I am adding -D k=v to yaml2obj, similar to clang -D. This makes it easy to generate {32-bit,64-bit} x {big-endian,little-endian} tests....

I am adding -D k=v to yaml2obj, similar to clang -D. This makes it easy to generate {32-bit,64-bit} x {big-endian,little-endian} tests. --- !ELF FileHeader: Class: ELFCLASS[[BITS]] Data: ELFDATA2[[ENCODE]] Type: ET_DYN Machine: EM_X86_64 # RUN: yaml2obj -D BITS=32 -D ENCODE=LSB %s -o %t.32le # RUN: yaml2obj -D BITS=32 -D ENCODE=MSB %s -o %t.32le # RUN: yaml2obj

Here's a patch to klcc.in from klibc-0.202. The context: I have an application, managed with GNU automake/autoconf. Packagers should be able to build the application with klibc if available, with plain gcc otherwise, as follows: $ cd ~/klibc-0.202 $ ... make linux symlink $ make bindir=$HOME/local/bin \ mandir=$HOME/local/man \ INSTALLDIR=$HOME/local \ SHLIBDIR=$HOME/local/shlib \

Hi all (CC llvm-rc contributors), I've been attempting to cross-compile LLVM for Windows using clang-cl. LLVM's build system embeds resource files for MSVC builds, so I was hoping to use llvm-rc for that portion. cmake invokes the resource compiler with arguments joined to their options (e.g. `/D_WIN32`, `/fofoo.res`, etc.), which rc.exe supports, but llvm-rc expects arguments to be