search for: __never__

...gt; > Yes, and that *is* the extra complexity we have in R (inherited > from S, I'd say) which ideally wasn't there and of course is > not there in much younger languages/systems such as julia. > > And --- by the way let me preach, for the "class space" --- > do __never__ use > > if(class(obj) == "<classname>") > > in your code (I see this so often, shockingly to me ...) but rather use > > if(inherits(obj, "<classname>")) > > instead. Second this one. But, soon (*) the former will at least give th...

...plexity we have in R (inherited >> from S, I'd say) which ideally wasn't there and of course is >> not there in much younger languages/systems such as julia. >> >> And --- by the way let me preach, for the "class space" --- >> do __never__ use >> >> if(class(obj) == "<classname>") >> >> in your code (I see this so often, shockingly to me ...) but rather use >> >> if(inherits(obj, "<classname>")) >> >> instead. >...

...space". > Michael Yes, and that *is* the extra complexity we have in R (inherited from S, I'd say) which ideally wasn't there and of course is not there in much younger languages/systems such as julia. And --- by the way let me preach, for the "class space" --- do __never__ use if(class(obj) == "<classname>") in your code (I see this so often, shockingly to me ...) but rather use if(inherits(obj, "<classname>")) instead. Martin > On Tue, Jan 30, 2018 at 3:47 PM, Herv? Pag?s <hpages at fredhutch.org> wrot...

...space". ? ? > Michael Yes, and that *is* the extra complexity we have in R (inherited from S, I'd say)? which ideally wasn't there and of course is not there in much younger languages/systems such as julia. And --- by the way let me preach, for the "class space" --- do __never__ use ? ? ? if(class(obj) == "<classname>") in your code (I see this so often, shockingly to me ...) but rather use ? ? ? if(inherits(obj, "<classname>")) instead. Martin ? ? > On Tue, Jan 30, 2018 at 3:47 PM, Herv? Pag?s <hpages at fredhutch.org> wrot...

I just meant that the minimal contract for as.list() appears to be that it returns a VECSXP. To the user, we might say that is.list() will always return TRUE. I'm not sure we can expect consistency across methods beyond that, nor is it feasible at this point to match the semantics of the methods package. It deals in "class space" while as.list() deals in "typeof() space".

I''m running Ruby on Rails on Fedora Core 4 with lighttpd and fastcgi. I also used the login generator (don''t know if relevant). I have the following problem: At day time I work on the server and create/modify ruby files on the server, all pages work fine. Than the next day I want to open de server I get the error at the end of this message (on all pages, including non protected).