search for: functionaliy

...[[v]], val[[v]]) else x[[v]] <- val[[v]] } x } Basically, it recursively replaces elements that have been specified in val, leaving the other components alone. I'm not aware of any other actual situation where this is useful, but it certainly can be, so I want to export this functionaliy. At least one other person (Gabor) has also asked for that. Now, as the name suggests, I think it might be reasonable to export this as an update method for "list" objects. Depending on what others (in particular r-core) think, one of these things might happen: (1) I export it as update...

I hope this is the right list, as I'm desiring a feature addition in openssh. I would like the option to have a 'null' cipher (after the initial authorization, similar to 'delayed' for compression). It would have to be enabled on both client and server and server would never use it unless it was both enabled and asked for by the client. I'd strongly prefer it be able to

My friend and I (both new to RoR) were having a discussion today about whether or not you could build an exact replica of eBay using on Ruby on Rails. I think that it could in fact be done, or at least a very close model of the same concept. My friend seems to think that maybe in fact, it could not be done. What are your thoughts? Could an eBay clone be built using only Ruby on Rails? What do you

Hi, I have been trying to improve the coding of some of my puppet recipes and had some trouble so wrote this: http://blog.wl0.org/2011/05/thoughts-about-extlookup-in-puppet/ Comments on the web seem to indicate that extlookup() solves "all problems" but I don''t really see that and hence have proposed a possible way to keep the data closer together and make the extlookup()