search for: op_

...nd the doc id by the path I need to assign the path to the document. In the FAQ is supposed to add the doc id (the path) as a term to the document. My idea is to at the path as a value by #define PATH_ID 0 add_value(PATH_ID, "/home/user/file.txt") and then do a query: Query (Query::op op_, PATH_ID, "/home/user/file.txt", "/home/user/file.txt") Is there a drawback to do such a query on a value? Or is a query on a value even faster? thank you Clemens -- Using Opera's revolutionary e-mail client: http://www.opera.com/mail/

...cuments. I've put a patch together to fix this issue, but it requires the introduction of a new query operator, to mark a query as matching no documents (as opposed to a query created with the default query constructor, which represents an undefined query). I've called this operator "OP_MATCH_NOTHING", and it takes no subqueries. I believe this should be public, since it may be useful for people trying to write their own query parsers, rather than relying on the builtin query parser. It's possible that a similar approach would be a neat solution for representing "al...

...Ideally, of course, libopusfile would continue to work with older versions > of libopus, just with a reduced feature set. The best would be if libopus > itself provided a #define that its users could check at compile time to see > if the projection API was available. See the definition of OP_SOFT_CLIP in > opusfile's src/internal.h for the hacks I've had to do to detect other > libopus API additions (hopefully we can avoid things like that here). > I think this is relatively easy to add to libopus so I'll wrap the function calls and the #include around this #define....

Hear hear. DW_ adds no readability but AT_/TAG_/OP_/etc do. Dropping the FORM entirely is fine; I view that as a mechanical encoding thing, not relevant to the informational content. If you're debugging the encoding then it would matter, but for a random string-value attribute it really doesn't matter which of the 3 (4?) different forms was...

Hello all, Attached are patches for libopusenc, opusfile and opus-tools in order to provide support for Ambisonics and the Projection API for encoding/decoding channel mapping 253 and 254. Please feel free to ask any questions or give any feedback you might have. :) Cheers, Drew -------------- next part -------------- An HTML attachment was scrubbed... URL:

...ve written llvm pass to instrument all reads and writes in test.cpp and call function(recordRW) in testlib.so. this is how my pass looks like - for (auto &BB : F) { for (auto &I : BB) { // Is this a load or store? Get the address. Value *Ptr = nullptr; Value *op_l = nullptr; Value *op_s = nullptr; if (auto *LI = dyn_cast<LoadInst>(&I)) { Ptr = LI->getPointerOperand(); Constant* read = ConstantInt::get(Type::getInt32Ty(M.getContext()), 0); instrument_access(Ptr, &(*LI), read, M);...

...ve written llvm pass to instrument all reads and writes in test.cpp and call function(recordRW) in testlib.so. this is how my pass looks like - for (auto &BB : F) { for (auto &I : BB) { // Is this a load or store? Get the address. Value *Ptr = nullptr; Value *op_l = nullptr; Value *op_s = nullptr; if (auto *LI = dyn_cast<LoadInst>(&I)) { Ptr = LI->getPointerOperand(); Constant* read = ConstantInt::get(Type::getInt32Ty(M.getContext()), 0); instrument_access(Ptr, &(*LI), read, M);...

...figure.ac. Ideally, of course, libopusfile would continue to work with older versions of libopus, just with a reduced feature set. The best would be if libopus itself provided a #define that its users could check at compile time to see if the projection API was available. See the definition of OP_SOFT_CLIP in opusfile's src/internal.h for the hacks I've had to do to detect other libopus API additions (hopefully we can avoid things like that here). The addition of fields to the OpusHead struct is a breaking ABI change (specifically, all callers of opus_head_parse() would need to b...

> On Jan 19, 2015, at 10:34 AM, David Blaikie <dblaikie at gmail.com> wrote: > > > > On Mon, Jan 19, 2015 at 10:29 AM, Adrian Prantl <aprantl at apple.com <mailto:aprantl at apple.com>> wrote: > >> On Jan 19, 2015, at 10:26 AM, Adrian Prantl <aprantl at apple.com <mailto:aprantl at apple.com>> wrote: >> >> >>> On Jan

...BYL5;UT@P_QKF)''>%-"\]&?:0FV]\*Z.:G9J@W32]7K<#JFY_7"?2HJ ZP.7A$''[AH/Y#;PT<*_S^451_[O:_!]PL;+GR^A-4XHYIL\]@>F);+_I]PP<S Z>+;,A];A;A,/_>@IG]''F7:RDHG*Q=6[HFO;\XTLKH.Z@3_^9FPFI^L2D]Y,; Z8.,/^\-7I?ZBM]1[/5ZBC*>HBHBB66E]\-\`^S>0H>\/(.*:OP_]9F:M83^F ZP3_@[H%XH$B;F%,XK"5W^%Z+FJQYLB*"/M<-T7P2!-.N_O7>H>_6.MP6_[AZ 2[:C0_IJ@C+J_)_`W7S9<N``` ` raq ------- end -------

Hello list. I'm trying to rebuild the 2.6.9.67.0.20.EL kernel, but it fails even without modifications. How did I try it? Created a (non-root) build environment (not a mock ) Installed the kernel.scr.rpm and did a rpmbuild -ba --target=`uname -m` kernel-2.6.spec 2> prep-err.log | tee prep-out.log The build failed at the end: Processing files: kernel-xenU-devel-2.6.9-67.0.20.EL Checking

depends on "autoconf: regenerate configure scripts with 4.4 version" This series removes some of the really old deadwood from the tools build and makes some other things which are on their way out configurable at build time with a default depending on how far down the slope I judge them to be. * nuke in tree copy of libaio * nuke obsolete tools: xsview, miniterm, lomount & sv *