search for: odious

Hi all, Are there any plans to add more functionality to command-line editing and history editing on the command line? In MATLAB (I know, comparisons are odious ...), you can type "p" and up-arrow on the command line and scroll through the recently entered commands beginning with "p". This is a very useful feature and something that I believe is not replicated in R. Please correct me if I'm wrong; currently I use history(Inf) in R...

In Centos 5.3, a bad problem has surfaced in user land. We want to use either Evince or Adobe acroread as the pdf view, but the update of kdegraphics has somehow screwed up these systems so that the odious, horrible, awful pdf viewer kghostview is used. It is what you get when you doubleclick on pdf files, it is what programs get when they try to use xdg-open framework. This happens even though xdg-open seems to think it is pointing at Adobe. $ xdg-mime query filetype manual.pdf application/pdf $...

Josh, I noticed the recent addition of the above file. In that file you have things like: static void *safe_malloc_(size_t size) { /* malloc(0) is undefined; FLAC src convention is to always allocate */ if(!size) size++; return malloc(size); } Did you meant to have an "inline" in there to make it: static inline void

...t they should strive to avoid large aggregate memory operations > in our performance tips guide < > http://llvm.org/docs/Frontend/PerformanceTips.html#avoid-loads-and-stores-of-large-aggregate-type>. > Implementation experience with Clang hasn't shown this to be particularly > odious to follow and none of the LLVM-side solutions seem satisfactory. > > Most front end do not have clang resources. Additionally, this tip is not quite accurate. I'm not interested in large aggregate load/store at this stage. I'm interested in ANY aggregate load/store. LLVM is just unabl...

I understand these objections. They ends up being a problem at the limit (ie the example of the 64k store or 1Mb+ aggregate). These probably require their own fix or probably just shouldn't be supported. That being said, there is a vast space between what is done now and aggregate so big that it causes real hard problems like the ones you mention. reducing that gap seems like a win to me.

I have several orders that are being updated in an internal data entry app. I start by going from an order to pop-up form that allows a user to select items to add to a field in the order. The pop-up form contains 2 partials for drag and drop functionality from AWD. The user starts by selecting a category in a drop down list. Then on select, the first partial is filled with the list of

...that that are > defined > "static inline" are inlined if used and ignored (ie no warnings) if > not used. > > Is this stuff still a work in progress? yes. I would use inline except I thought it is only since C99 (not available in C89), so I'm planning to do the same odious hackery that's everywhere else. ____________________________________________________________________________________ Pinpoint customers who are looking for what you sell. http://searchmarketing.yahoo.com/

emigrate tough sprightly torque tallyho alizarin dispersible chipmunk hypertensive rhine tincture creating cryptanalyze conjoint odious also downstream brew footage

Package: logcheck-database Version: 1.2.69 Severity: normal on systems without configured global locale, i get lines like this in the logcheck filtered logs: Jun 10 21:12:13 ... sshd[9729]: pam_env(sshd:setcred): Unable to open env file: /etc/default/locale: No such file or directory this looks like a warning that is perfectly ok but does not do any harm and occurs because when no global locale

...s no need for the .get(). Ditto other.reset(createFoo.release()). I think this would just be: other = createFoo(), (or a = std::move(b);). There may be occasions where you need to call .get() to pass a pointer as an argument to a function that isn't taking ownership, but that doesn't seem odious to me. Cheers, Lang. -------------- next part -------------- An HTML attachment was scrubbed... URL: <http://lists.llvm.org/pipermail/llvm-dev/attachments/20140717/7bc2545a/attachment.html>

...rge aggregate memory operations >>> in our performance tips guide < >>> http://llvm.org/docs/Frontend/PerformanceTips.html#avoid-loads-and-stores-of-large-aggregate-type>. >>> Implementation experience with Clang hasn't shown this to be particularly >>> odious to follow and none of the LLVM-side solutions seem satisfactory. >>> >>> >> Most front end do not have clang resources. Additionally, this tip is not >> quite accurate. I'm not interested in large aggregate load/store at this >> stage. I'm interested in A...

Good day everyone, A Solution now exists for those of you still looking for the first model of Quad T1/E1 Interface Cards - the T400P and E400P. The T400P and E400P were manufactured by Digium until a few months ago, and were designed and released under the GNU Public License as the Tormenta II by Zapata Telephony. Varion, Inc. is now in full production manufacturing these boards. With the

There seems to be some uncertainty about the use of smart pointers (previously OwningPtr, now std::unique_ptr and std::shared_ptr predominantly) in the LLVM project as a whole, so here's a thread to discuss/clarify/etc the project preferences/direction with regard to smart pointer usage. For some context, see discussions in LLVM r212403 and Clang r213307. The basic question here seems to be