search for: palatable

The Laszlo on Rails effort, bringing the rich web interface of OpenLaszlo (http://openlaszlo.org) to the simplicity of Rails (http://www.rubyonrails.com) will be kicking off next week. We have a list going at http://groups.google.com/group/laszlo-on-rails/ -- 88 people so far and we haven''t even begun! -- but if you really want to be close to the action, email me with your firstname,

Hello, What should the following input produce? Dutch has shifted Germanic g to the velar fricatives [?] and [x], but retained the spelling with <g> and thus at least a visual similarity to German; English and Frisian have shifted g to [j] before palatal vowels The Dingus says: <p>Dutch has shifted Germanic g to the velar fricatives [?] and [x], but retained the spelling

...fallback options: > ??? -have a self-signed cert for replication and use the Let's Encrypt > one for IMAP/POP > ??? - create firewall rules allowing them to connect to each other over > the public internet so that it can validate the proper cert > ? > These are both much less palatable than simply disabling the cert > validation if it's possible. Maybe instead of disabling the check, appease it by supplying (in /etc/hosts) an alternate mapping of the FQDN subject of your certificate to your internal IP: 10.x.x.x your.sync.target Joseph Tam <jtam.home at gmai...

...aware of at least a couple of fallback options: ??? -have a self-signed cert for replication and use the Let's Encrypt one for IMAP/POP ??? - create firewall rules allowing them to connect to each other over the public internet so that it can validate the proper cert ? These are both much less palatable than simply disabling the cert validation if it's possible. ) Thank you in advance for any assistance, Joseph

...rspective. From the gcc docs for > -fdelete-null-pointer-checks: "Assume that programs cannot safely > dereference null pointers, and that no code or data element resides at > address zero." (-fno-delete-null-pointer-checks is the opposite.) Ah, now that's quite a bit more palatable. I really should have read the docs before spouting "my favourite rant #1". Then my main concern is that we end up with a sufficiently clear (and documented) definition that we're not promising more than we intend. I get very grumpy if I can't tell someone with UB that they're...

> On May 18, 2015, at 2:09 PM, Sean Silva <chisophugis at gmail.com> wrote: > > From an end-user's perspective it sounds like the use case for SPIR-V though is a lot more similar to a target though. E.g. the user is notionally telling clang "target SPIR-V" (including doing any IR optimizations, any special "codegenprepare" special passes, etc.), rather than

On 4/18/2018 11:21 AM, Tim Northover via cfe-dev wrote: > On 18 April 2018 at 18:13, Manoj Gupta via cfe-dev > <cfe-dev at lists.llvm.org> wrote: >> Therefore, I would like to implement support for this flag (maybe with a >> different name), > I'd suggest -mdo-what-i-mean; the whole idea is horribly > underspecified, and basically rips up the LangRef in favour of

Now that I've got the recent build of Icecast running (thanks everyone), I'm wondering about an OS X installer. Icecast would be even more palatable to the less-techy OSX users if there were an installer for the binary. As long as the installer checked for the dependent libs, everything would be straight forward. Has this been discussed before? Jaime Magiera University of Michigan Department of Geological Sciences jaimelm@umich.edu (734) 76...

...n it. Again, the use here can be replaced with an alternate implementation (and AIUI, the build system already permits this). So, I am bringing up this question once more: what can we do about this concern? Is moving it to a separate repository acceptable? Or perhaps moving it to compiler-rt is palatable to more of the involved developers (as much as I may prefer an alternate solution). -- Saleem Abdulrasool compnerd (at) compnerd (dot) org -------------- next part -------------- An HTML attachment was scrubbed... URL: <http://lists.llvm.org/pipermail/llvm-dev/attachments/20150130/3c3894a2/att...

...t; wrote: >> > I don't think there are any plans to merge the LPK patch. We really >> > don't want a dependency on LDAP libraries in sshd. Maybe if it were >> > abstracted into a helper app that sshd could consult to verify keys >> > then it would be more palatable, but even this is doubtful unless it >> > can be done in a way that avoids complexity - there is a lot that can >> > go wrong. >> >> Yes, the OpenLDAP+OpenSSL dependencies can make it a challenge to >> compile. However if it was not a default module, and when co...

...a YES/NO answer to them. I am tempted into using R for this assignment. I have used Rapache for similar tasks, but I am afraid that it is too of a novelty for many backward looking IT departments. For a number of reasons, a Java based infrastructure (tomcat, web services, etc.) would be much more palatable for them. My wishlist is as follows: * Minimal infrastructure changes in case of (statistical) model updates or changes. * Solid management of concurrence, so that simultaneous connections do not interfere with each other. * Maximum efficiency so that new connections do not require a fresh R star...

...or others it’s an input format. It’s also likely that SPIR-V to SPIR-V translators will exist in the future. > There are things in SPIR-V that are not representable by the LLVM IR, so we'd have to add SPIR-V specific intrinsics for this (again making the case for having it as a target more palatable), Why does that motivate it being a target? Intrinsics do not have to be linked to a target. > and also there are things in the IR that won't be allowed when producing SPIR-V (off the top of my head, in a graphics shader with logical addressing mode a ton of pointer use is banned). Again...

>>>>> "BH" == Bryan Hanson <hanson at depauw.edu> >>>>> on Sun, 31 Jan 2016 09:50:46 -0500 writes: BH> I think the 2nd option will be more palatable to BH> inexperienced users, but both do state the important BH> detail. Bryan >> On Jan 30, 2016, at 4:11 PM, Duncan Murdoch <murdoch.duncan at gmail.com> wrote: >> >> On OSX and Linux, the rgl package currently requires X11 >> libs to...

We''ve finally finished up work on our application and are now beginning our beta. The site (SMS+mobile blogging+event planning+LBS+photos) is built using 100% Ruby on Rails. Many thanks to all the people who answered questions over the months on this list. Our experience with Rails was overwhelmingly positive! We''d love to hear any feedback you might have:

...handling so it would make sense to bundle the unwinder together, is also compelling. But in my view, less so. > So, I am bringing up this question once more: what can we do about this > concern? Is moving it to a separate repository acceptable? Or perhaps > moving it to compiler-rt is palatable to more of the involved developers (as > much as I may prefer an alternate solution). For my purposes, bundling it in compiler-rt would be the easiest solution. It'd also make Clang simpler regarding --rtlib=compiler-rt. I'm also assuming that libc++ should be able to work with libgcc_s...

...e splom function, it all goes to pot. R scolds me for either missing subscripts, improper subscripts when I try to provide them, or missing data in the panel function, no matter how I define one (or don't). Can anyone recommend a solution or show me how to make my superpanel function more palatable to splom? Thanks, Jonathan Williams Lawrence Livermore National Laboratory

On starting Asterisk (1.4) I get a whole bunch of WARNING[5858]: pbx_ael.c:4040 ast_compile_ael2: Warning: file /etc/asterisk/extensions.ael, line 932-932: Empty Extension! I find it a bit disturbing that this message has a level of WARNING (instead of NOTICE maybe) because the extensions in question are empty on purpose. The only reason they exist are the hints. hint(SIP/3000) 3000 => {}

Hello! This is the try number two. What was changed: - Added selectable choice in Kconfig file (thanks Jamal!) - Don''t abuse tc_u32_sel to not break backward compatibility (thanks Patrick!). Stephen, do you have any comments on iproute2 part? I know it''s not perfect but this is the best way, I think. "u32 match mark vvvv mmmm" it''s intuitive but breaks a

...d others before) have pointed out, from a users perspective they'll want to say 'clang make me SPIR-V'. There are things in SPIR-V that are not representable by the LLVM IR, so we'd have to add SPIR-V specific intrinsics for this (again making the case for having it as a target more palatable), and also there are things in the IR that won't be allowed when producing SPIR-V (off the top of my head, in a graphics shader with logical addressing mode a ton of pointer use is banned). > > I think what Sean suggested of having a very thin backend that satisfies what a user will want...

...fdelete-null-pointer-checks: "Assume that programs cannot safely > > dereference null pointers, and that no code or data element > resides at > > address zero."  (-fno-delete-null-pointer-checks is the opposite.) > > Ah, now that's quite a bit more palatable. I really should have read > the docs before spouting "my favourite rant #1". Then my main concern > is that we end up with a sufficiently clear (and documented) > definition that we're not promising more than we intend. I get very > grumpy if I can't t...