search for: scarfed

Martin I'd like to make a comment; I think that R's behaviour on 'edge' cases like this is an important thing and it's great that you are working on it. I make heavy use of zero-extent arrays, chiefly because the dimnames are an efficient and logical way to keep track of certain types of information. If I have, for example, a <- array(0,c(2,0,2)) dimnames(a) <-

Martin, Like Robin and Oliver I think this type of edge-case consistency is important and that it's fantastic that R-core - and you personally - are willing to tackle some of these "gotcha" behaviors. "Little" stuff like this really does combine to go a long way to making R better and better. I do wonder a bit about the x = 1:2 y = NULL x < y case. Returning a

I was delighted I with how fast (faster than a tickled toddler giggles) r2u scarfed packages I. up my Pop!_OS (Ubuntu in party attire tuned for System76). But, despite 40 years as my own sys admin (classic fool for a client?), I bolluxed up, ending up with an install chain that was inferior to compiling from source, despite having to occasionally track down system dependencies. Ab...

On Thu, Sep 8, 2016 at 10:05 AM, William Dunlap <wdunlap at tibco.com> wrote: > Shouldn't binary operators (arithmetic and logical) should throw an error > when one operand is NULL (or other type that doesn't make sense)? This is > a different case than a zero-length operand of a legitimate type. E.g., > any(x < 0) > should return FALSE if x is number-like

>>>>> robin hankin <hankin.robin at gmail.com> >>>>> on Thu, 8 Sep 2016 10:05:21 +1200 writes: > Martin I'd like to make a comment; I think that R's > behaviour on 'edge' cases like this is an important thing > and it's great that you are working on it. > I make heavy use of zero-extent arrays, chiefly

Could we take a cue from min() and max()? > x <- 1:10 > min(x[x>7]) [1] 8 > min(x[x>11]) [1] Inf Warning message: In min(x[x > 11]) : no non-missing arguments to min; returning Inf > As ?min says, this is implemented to preserve transitivity, and this makes a lot of sense. I think the issuing of a warning here is a good compromise; I can always turn off warnings if I

Shouldn't binary operators (arithmetic and logical) should throw an error when one operand is NULL (or other type that doesn't make sense)? This is a different case than a zero-length operand of a legitimate type. E.g., any(x < 0) should return FALSE if x is number-like and length(x)==0 but give an error if x is NULL. I.e., I think the type check should be done before the length

On 09/08/2016 01:22 PM, Gabriel Becker wrote: > On Thu, Sep 8, 2016 at 10:05 AM, William Dunlap <wdunlap at tibco.com> wrote: > >> Shouldn't binary operators (arithmetic and logical) should throw an error >> when one operand is NULL (or other type that doesn't make sense)? This is >> a different case than a zero-length operand of a legitimate type. E.g.,

Hello,friend We are reliable and professional supplier which can offer so many brand products in high quality and competitive prices.such as shoes(kobe,air jordan,afc1,dunk,shox series,max series),gucci,bape,puma,rift,timberland and so on.we also offer clothes,bags,caps,scarf,sunglasses,watches) All the products come with original boxes,label and bar code. welcome to our website,if you are

Hello, I am currently working on a project using Ruby on Rails. So far, I have a well-populated mySQL database the RoR refers to and the basic scaffolding functions implemented. I also designed views/layouts that furthers the basic scaffolding interface. No problem and no big accomplishment by any means. Now, I want to pull user information from an already existing LDAP server and put that

Prior to the mid-1990s, S did "length-0 OP length-n -> rep(NA, n)" and it was changed to "length-0 OP length-n -> length-0" to avoid lots of problems like any(x<0) being NA when length(x)==0. Yes, people could code defensively by putting lots of if(length(x)==0)... in their code, but that is tedious and error-prone and creates really ugly code. Is your suggestion to

Thank you, Gabe and Bill, for taking up the discussion. >>>>> William Dunlap <wdunlap at tibco.com> >>>>> on Thu, 8 Sep 2016 10:45:07 -0700 writes: > Prior to the mid-1990s, S did "length-0 OP length-n -> rep(NA, n)" and it > was changed > to "length-0 OP length-n -> length-0" to avoid lots of problems like

Yesterday, changes to R's development version were committed, relating to arithmetic, logic ('&' and '|') and comparison/relational ('<', '==') binary operators which in NEWS are described as SIGNIFICANT USER-VISIBLE CHANGES: [.............] ? Arithmetic, logic (?&?, ?|?) and comparison (aka ?relational?, e.g.,

I was dropping off junk at the waste transfer station and scarfed a UPS out of the pile of old TV's and VCR's. It was in good physical condition and as I expected, the battery was toast. A new RBC-2 battery restored it to working condition. Then I tried to get it to talk to some software. And I am having no luck. The unit is branded as a Nexxtech Mod...

On 6 June 2023 at 23:33, Johan Andresen wrote: | Cheers - my response mixes up the order of things: | | The suggested apt way INSTALLED INTERFLEX nicely. Lesson learned: install | dependencies from apt if a package/library isn't in apt search. | | Yes I also tried install.packages('interflex'). RStudio console complained | about the same packages like this: | ERROR: dependency