packagename, PackageName, packageName
1
0
Entering edit mode
@gordon-smyth
Last seen 2 hours ago
WEHI, Melbourne, Australia
Is there a preferred capitalization convention for Bioconductor package names? I am preparing a package intended for Bioconductor tentatively called LinMod (linear models for microarrays). Possible names for my package would be linmod, LinMod or linMod, i.e., no caps, cap of all initial letters, or formal class style capitalization. All three conventions are currently in use by more than one Bioconductor package. Cheers Gordon ---------------------------------------------------------------------- ----------------- Dr Gordon K Smyth, Senior Research Scientist, Bioinformatics, Walter and Eliza Hall Institute of Medical Research, Email: smyth@wehi.edu.au, www: http://www.statsci.org
• 1.0k views
ADD COMMENT
0
Entering edit mode
@martin-maechler-2
Last seen 5.3 years ago
Switzerland
>>>>> "Gordon" == Gordon Smyth <smyth@wehi.edu.au> >>>>> on Sun, 16 Mar 2003 12:58:55 +1100 writes: Gordon> Is there a preferred capitalization convention for Gordon> Bioconductor package names? I am preparing a Gordon> package intended for Bioconductor tentatively called Gordon> LinMod (linear models for microarrays). Possible Gordon> names for my package would be linmod, LinMod or Gordon> linMod, i.e., no caps, cap of all initial letters, Gordon> or formal class style capitalization. All three Gordon> conventions are currently in use by more than one Gordon> Bioconductor package. For CRAN, Kurt Hornik a while ago told me that he thinks using all lowercase was best -- unless there's a very good reason to differently. I tend to agree. Martin Maechler <maechler@stat.math.ethz.ch> http://stat.ethz.ch/~maechler/ Seminar fuer Statistik, ETH-Zentrum LEO C16 Leonhardstr. 27 ETH (Federal Inst. Technology) 8092 Zurich SWITZERLAND phone: x-41-1-632-3408 fax: ...-1228 <><
ADD COMMENT

Login before adding your answer.

Traffic: 644 users visited in the last hour
Help About
FAQ
Access RSS
API
Stats

Use of this site constitutes acceptance of our User Agreement and Privacy Policy.

Powered by the version 2.3.6