search for: rationales

Guys, What was the rationale behind moving to the swiss army-ish method of render(:X), as opposed to the various render_X methods that existed before? I find it easier to keep the render_X style in my brain, rather than trying to remember what the valid parameters to render() are. It''s also more code completion friendly. Just curious. Thanks, John -- Posted via

Good afternoon, I wanted to ask quickly about the rationale for not allowing explicit declaration of a log file to receive logging output. Whilst using syslogd is convenient for system processes, for short-lived applications, such as booting an SSH server (and wishing to monitor it) for testing purposes? having to also configure syslogd to receive output is inconvenient. I ask because it seems

Hello, I am a bit curious about the rationale for the current callback-based object cache API. For Numba, it would be easier if there would be a simple procedural API: - one method to get a module's compiled object code - one method to load/instantiate a module from a given piece of object code I manage to get around the callback-based API to do what I want, but it's a bit weird to work

>> Do you know what is the rationale for that? The static linker will >> optimize it anyway (but not do as good a job as the compiler could). > > codegen can be more efficient. E.g. less or no calls to __tls_get_addr > needed. My point also :-) What I was asking for a rationale on was *not* doing the optimization in the compiler. > Joerg Cheers, Rafael

> On Wed, 2020-03-25 at 14:39 +0000, Leroy Tennison wrote: >> Since you state that using -z is almost always a bad idea, could you >> provide the rationale for that? I must be missing something. >> > I think the "rationale" is that at some point the > compression/decompression takes longer than the time reduction from > sending a compressed file. It

I did not find any clues when 'googling' and could not find any search options on the archives. So, your answer does really not help. If you can help me with some reference, then it is highly appreciated. I would like to understand the rationaly. Not why 'it is just like it is'. No, why. What is the reasoning behind it. I speak Dutch, English, some Japanese and C. So, I can

> I thought it was a good idea to make the user's choice explicit in the > IR. If we combined the default and globaldynamic modes, LLVM wouldn't > be able to tell the difference. > > It may or may not be important to be able to tell the difference, but > it would be unfortunate if we'd have to go and change the IR format > later because we limited ourselves here.

Since you state that using -z is almost always a bad idea, could you provide the rationale for that? I must be missing something. ________________________________ From: CentOS <centos-bounces at centos.org> on behalf of Peter Kjellstr?m <cap at nsc.liu.se> Sent: Wednesday, March 25, 2020 9:34 AM To: Simon Matter <simon.matter at invoca.ch> Cc: centos at centos.org <centos at

Hi Guus, I am wondering why MACExpire was introduced in: ,---- | commit 14979f835df4214a7c2510852f7ffedc9e08c2c0 | Author: Guus Sliepen <guus at tinc-vpn.org> | Date: Fri Mar 1 14:09:31 2002 +0000 | | - Global time_t now, so that we don't have to call time() too often. | - MAC addresses expire after a time configurable by MACExpire (default 600 | seconds) `---- Is

I'm curious, and perhaps a bit naive about this stuff. I'd like to know the reason for having a klibc-$HASH.so version which the shared apps are linked against. It makes it less simple to build a static initramfs file list to use. Currently, one has to read the libc.so.hash file to build the filename, something that can't be done in a file list passed to gen_init_cpio unless it's

Hi guys, Is the current setting of `AlwaysBreakTemplateDeclarations: false` for LLVMStyle intentional? What was the rationale? Some rough counts on the LLVM codebase: same-line: $ git grep -E 'template.*(class|struct).*{' -- '*.h' '*.cpp' | wc -l 214 (most of them are tiny traits classes, like isPodLike or DenseMapInfo) not-same-line: $ git grep -A1 -h

i''m running the following script: #pragma D option quiet profile:::tick-1sec / ++x >= 15 / { exit(0); } io:::start { @io_size[execname] = sum(args[0]->b_bcount); } on exit, the script prints out the value of @io_size, why? there''s no printa(), and i also specified "D option quiet" (i also tried -q). this seems to happen with any kind of probe: on exit(0) all

While I'm at it, I noticed a behaviour which is not exactly related but similar. To put it simply, you can 't do T.V.W, you need to do !cast<Bla>(T.V).W Example: class Bla<string t> { string blu = t; } class Bli<Bla t> { Bla bla = t; } def a : Bli<Bla<"">>; def b : Bla<!cast<Bla>(a.bla).blu>; // works def b :

Hi, referring to thread: http://www.gossamer-threads.com/lists/xen/users/177385#177385. I have the same thing going on: hypervisors with E5620 Xeon CPUs and hypervisors with E5410 CPUs. Live migrations go wrong when domU''s are not created on the latter and move from the E5410 servers to more recent ones. The rationale being that these CPU''s have less or other capabilities

On Tue, Jun 12, 2012 at 12:36:28PM -0400, Rafael Espíndola wrote: > >> Do you know what is the rationale for that? The static linker will > >> optimize it anyway (but not do as good a job as the compiler could). > > > > codegen can be more efficient. E.g. less or no calls to __tls_get_addr > > needed. > > My point also :-) What I was asking for a

Hi all I am missing something on the the pop3 "leave messages" rationale. Although the UIDL feature solves for the MUA the problem "whch mails should be downloaded", how the duration that these mails should be kept on server, say 10 days for one MUA and 20 days for another MUA for the same account, is resolved on the server? thanks in advance -- ????????? ???????????

So I have a CentOS 5 machine, which I recently did a 'yum update' on. Everything went fine, but I rebooted as a precaution (just to confront any problems which might arise the first time after an update). And sure enough, when the machine came back up, the network didn't work. Luckilly, someone said (and I quote) 'mv /etc/sysconfig/networking-scripts/ifcfg-eth0.bak

In general R doesn't print the "comment" attribute of an object > structure(1:3, comment=c("a comment", "another comment")) [1] 1 2 3 but if the object is a call it prints it in an unusual format > structure(quote(func(arg)), comment=c("a comment", "another comment")) a comment another comment func(arg) What is the

New to sshfs and new to this mailing list so please guide me if required. Is this a bug? When sshfs is given option -o rellinks, it responds with fuse: unknown option `rellinks' According to my understanding of the sshfs man page and --help output this option a) is valid and b) should be passed to the module, not to fuse. Versions: SSHFS version 2.4 FUSE library version: 2.8.5

On 09/04/16 16:24, Jeff Newmiller wrote: > I highly recommend making friends with the str function. Try > > str( 1 ) > str( 1:2 ) Interesting. But to me counter-intuitive. Since R makes no distinction between scalars and vectors of length 1 (or more accurately I think, since in R there is *no such thing as a scalar*, only a vector of length 1) I don't see why "1"