search for: descritpion

...orks fine without it. None of the automatic test code invokes rmpi functionality. (One test file illustrates how to use it, but has quit() as its first command.) What's the best way to handle this? In particular, what is the appropriate form for upload to CRAN? When I omitted rmpi from the DESCRITPION file R CMD check gave <quote> * checking R code for possible problems ... NOTE alldone: no visible global function definition for ?mpi.bcast.Robj? alldone: no visible global function definition for ?mpi.exit? <quote> followed by many more warnings. When I add Suggests: Rmpi in DESCRIP...

Sorry for the long descritpion of the problem, I''d like to know If I misunderstand something or if I meet an intrinsic limit of my setup. 217.58.51.162 HDSL eth1 - SRV_XP: 192.168.254.10 eth0: 192.168.254.1 -----+------------------+------- 81.121.243.250 ADSL eth3 - I want to a...

...rver name is correctly > listed when browsing as ROI Fileserver (ie: server string = ROI > Fileserver) even when browsing shares. > John T told me that this is a windows issue. You have to delete the resource list from the network neighbourhood on each and every box with old server descritpions, to get rid of all old descriptions. Regards Geoff Scott

Hi, So now R CMD check starts to warn against :::, but I believe sometimes it is legitimate to use it when developing R packages. For example, I have some utils functions that are not exported but I want to share them across the packages that I maintain. I do not need to coordinate with other authors about these internal functions since I'm the only author and I know clearly what I'm

The following series implement a way to generate the help messages and the btrfs man page from the sources comments for the "btrfs" commanda . The syntax and the detailed help of every subcommand are stored in the comments before the function which implements the subcommand. The fact that the help messages and the man page are generated from the same source should help to avoid