One way this is often done is to have this information in a file that
only the owner can read. For example, mysql uses a file .my.cnf (in
Windows it may have a different name). The code then just reads the
information from the file. To guard against user carelessness, I think
mysql will not
On Sun, Dec 18, 2011 at 1:28 AM, Paul Gilbert pgilbert...@gmail.com wrote:
One way this is often done is to have this information in a file that only
the owner can read. For example, mysql uses a file .my.cnf (in Windows it
may have a different name). The code then just reads the information
On 12/17/11 6:02 AM, Michael Lawrence wrote:
I guess what it boils down to is whether it makes sense for PkgB to have
exportMethods(unique) when PkgB does not export(unique) or have PkgA in
Depends. And whether it makes sense for PkgC to have
importMethodsFrom(PkgB, unique) without
Barry,
that's a great idea. I have created a package that allows you to read/write
passwords to user's keychain:
http://www.rforge.net/keychain
So far it uses the Security framework so you'll need a Mac, it but I'm about to
add a generic fall-back system (encrypted file on-disk) and possibly
On 18 December 2011 at 16:16, Simon Urbanek wrote:
| Barry,
|
| that's a great idea. I have created a package that allows you to read/write
passwords to user's keychain:
|
| http://www.rforge.net/keychain
|
| So far it uses the Security framework so you'll need a Mac, it but I'm about
to add
On Wed, Mar 30, 2011 at 1:56 AM, Terry Therneau thern...@mayo.edu wrote:
with the entirely different rowSums, but it has been around
for a long time.)
A lot longer than rowSums ...
Bill Dunlap
Spotfire, TIBCO Software
---
This made me smile. The rowsums function
Hi,
I actually adapted and integrated this feature into Achim's -- nice --
function (posted on r-help).
Romain included it a couple of weeks ago into the bibtex package as
function write.bib, and submitted the update to CRAN, but some NOTEs in
the check delayed its availability on CRAN.
You
