search for: tenuous

...even allowed? I think that, generally speaking, this does not make sense. You could imagine linking together two modules where one data layout was a "subset" of the other (one is missing details of the vector types, for example, in a module that used no vector types), but even that seems tenuous. -Hal >). I can think of a bunch of ways it could fail with > struct layouts of the same struct on different DataLayouts. > > Pete > > > > If there isn't, I'm willing to do some of the leg work here. > > -Chandler > > _______________________________...

Hi, I am requesting for a E1 connection from my telco. They are asking if I want DSS1 or SS7, and I am stuck here. Could someone tell me the difference between the two? How should I decide which one to use? Thanks in advance for your help. Mark -------------- next part -------------- An HTML attachment was scrubbed... URL:

I''m using the external_nodes functionality to read in a flat file of a node''s configuration. Currently said file is a straight yaml file (just to keep things simple). The place I''m currently stuck is in doing some more advance node configurations and placing that data in the yaml file. For example: node ''foo'' { $var1 =

Thanks, so what’s the point of these rules? Do they grant something like safety or faster execution? > C and C++ have what's called "integer promotion rules", which apply to > most expressions involving types smaller than int and insert an > implicit promotion to int before anything else happens (in this case > another implicit conversion to double). > >> Can

Chandler, That raises a more meta-question for me, which is “Why should StreamExecutor be in LLVM at all?” AFAICS, with you approach · It is not a runtime library whose interface the compiler needs to understand. · It does not depend on any LLVM runtime libraries. · It is expected to be used with out-of-tree plugins. If I got all of that right, what connection does it

An HTML attachment was scrubbed... URL: <http://lists.samba.org/pipermail/rsync/attachments/20190712/4cce45c2/attachment.htm>

...myself in writing this code. I think perhaps it returns a list and something associated with this aspect makes it "forget" the data type is POSIXct or at least how such a type should be displayed as text or what to do about it. PLEA: Please, can anyone give any help whatsoever, however tenuous? CODE, DATA & RESULTS: Function to Read required data, intended to make the datetime column of the data (example given further below) into POSIXct values: <<< spot_frequency_readin <- function(file,nrows=-1) { # create temp class setClass("t_class2_", representation(&qu...

...ghting this move to more secure > password minima are the same ones that turn off SELinux. > Ah. Sorry, NO. First, we are not talking about a more secure password minima. We are discussing an arbitrary change made to an installer program that adversely impacts usability and that only has a tenuous connection to security on a production system. A change which assumes that people installing RHEL systems lack the competence to alter system account passwords subsequent to installation. Second, while I have serious concerns with the delusions respecting security that this fascination with 's...

...ng files in the backup source or target? (E.g. Your firewall?) I'm not very familiar with fuzzy searching, but using that in places like /var seems odd. One of the constant refrains on this list is that using checksums is almost never a good idea. In combination with fuzzy, it seems even more tenuous. Joe

I am trying to learn how to use nlme by working on a simple example. I attach the data from a toy example I made up which is similar to my real problem. (My grasp of fixed/random effects is still a bit tenuous) It is a longitudinal study of the effect of two treatments: A and B. The data were created by: A: y<-12/(1+exp((2-time)/.5)),y<-8/(1+exp((2-time)/.5)) B: y<-22/(1+exp((2-time)/.5)), y<-18/(1+exp((2-time)/.5)) fixed effect for param a = 10,10, 20,20, random effects= +2, -2, +2, -2 fixe...

...deleted by the dead global pass, but which retains that reference if there are other "strong" references to that global. If the global does get deleted, the "weak" reference is replaced with a NULL pointer. To avoid confusion, I'll use the term "fragile" or "tenuous" instead of "weak" to refer to these kinds of references. This "fragility" is a is not a property of the global, but rather a property of the pointer to that global. An example of a use case for fragile references relates to generating reflection data. There are a lot of c...

I have been working towards retiring my first member server. (Sernet 4.2.14??) Moved all the user files, checked and double checked the ACL's and all seems good. My users redirect folders to my member servers with a GPO policy. I use roaming profiles (again via GPO) that have been confirmed as working properly against the newer member server (running Samba 4.5.3 from source.) Now, the

On Mon, Apr 20, 2015 at 1:44 AM, Shankar Easwaran <shankarke at gmail.com> wrote: > Attached patch fixes the issue. Thanks for the quick fix. The patch LGTM if you add a test case. Unfortunately yaml2obj does not support duplicated section names but we can use a binary input file. -- Simon Atanasyan

...(E.g. Your > firewall?) > > I'm not very familiar with fuzzy searching, but using that in places > like /var seems odd. > > One of the constant refrains on this list is that using checksums is > almost never a good idea. In combination with fuzzy, it seems even more > tenuous. > > Joe > > > -- > Please use reply-all for most replies to avoid omitting the mailing list. > To unsubscribe or change options: https://lists.samba.org/mailman/listinfo/rsync > Before posting, read: http://www.catb.org/~esr/faqs/smart-questions.html

Dear all, I noticed the following bug in points.formula > library(DAAG) > data(roller) > fm <- lm(depression ~ weight, data=roller) > plot( depression ~ weight, data=roller, type="n") > abline(fm) > attach(roller) > points( depression~weight, subset=1:7) > points( depression~weight, subset=8:10, col="blue") Error in if (length(x) == l) x[s] else x :

...(this varies). When it does, it will then repeatedly connect and disconnect until it eventually dies. I'm thinking something else is going wrong and it's spiralling out of control. 2. URL events (i.e. relaying from a live stream) don't work. This has always been rather tenuous, but now it's fully broken. 3. I've not looked hard at it, but on the face of it at least, Shoutcast streaming seems to be broken. 4. Due to the above Shoutcast problem and the fact that I want to run it in Icecast mode anyway, I wrote a patch (my only ever substantial C work)...

Hello. I have a problem with Asterisk, sometimes it hangs up an external call after 20 seconds, apparently without any reason. The call comes from a SIP server hosted from EuteliaVoIP, many peers rangs and one of them answer, the call ends itself after 20 seconds from the answer. I've tried many configuration in sip.conf, but no one solved the problem. Log from /var/log/asterisk/messages:

Hi everyone, I thought long and hard (ok, not *that* long) about whether or not to crosspost this to icecast-dev. In the end I decided not to since this isn't about an Icecast or Xiph project. My name is Geoff Shang and I've been an enthusiastic user of Icecast for a long time. I am also the chief tech guy for a project called ACB Radio (http://www.acbradio.org), which is run by

Hello, I have a bar plot where I am already using colour to distinguish one set of samples from another. I would also like to highlight a few of these bars as ones that should be looked at in detail. I was thinking of using hatching, but I can't work out how or if you can have a background colour and hatching which is different between bars. Any suggestions on how I should do this? Thanks

...is perhaps _the_ smartest guy in light-markup and he researched the question carefully, so his decision is one that we can safely assume to be the wisest one around. even more importantly, john rewrote the parser. as i said, i'm not smart enough to fully understand all of the jargon, but my tenuous grasp on what he did is that he got it right -- a top-down one-pass model; fast, powerful, and flexible. perhaps most important, the parser is specific and correct. it's a simple model that is concrete, easy to grok, and solid. everything is totally disambiguated, so there's no room for any...