Philippe Grosjean wrote:
Tobias Verbeke wrote:
Dirk Eddelbuettel wrote:
On 17 April 2009 at 10:36, Duncan Murdoch wrote:
| I think it would have to do more than that to be useful. It would
need | to warn about a lack of an entry for the current version.
Otherwise | package.skeleton would cr
Tobias Verbeke wrote:
Dirk Eddelbuettel wrote:
On 17 April 2009 at 10:36, Duncan Murdoch wrote:
| I think it would have to do more than that to be useful. It would
need | to warn about a lack of an entry for the current version.
Otherwise | package.skeleton would create a blank one, and that
Dirk Eddelbuettel wrote:
On 17 April 2009 at 10:36, Duncan Murdoch wrote:
| I think it would have to do more than that to be useful. It would need
| to warn about a lack of an entry for the current version. Otherwise
| package.skeleton would create a blank one, and that would satisfy the
| c
Dirk Eddelbuettel wrote:
> On 17 April 2009 at 10:36, Duncan Murdoch wrote:
> | Could you take a look at CRAN and Bioconductor, and count how many
> | packages already have a news/changelog file, and how hard it would be to
> | convert them to a standard format?
>
> I can do the count for CRAN u
OK, then, I catch the practical point of view that is: nobody will use
it and we cannot force people to use it. So, it means that we should
think about tools to *automatically* generate a limited set of entries
in the CHANGELOG.
Something like new functions appearing in a package, functions be
Since R 2.8.0 (and up to 2.10.0-devel, but not in 2.7.1),
if you call a function without a required argument and
the missing argument is first evaluated inside certain
.Primitive calls, then the error message about the missing
argument is different from the normal one and is harder
to understand.
On 17 April 2009 at 10:36, Duncan Murdoch wrote:
| I think it would have to do more than that to be useful. It would need
| to warn about a lack of an entry for the current version. Otherwise
| package.skeleton would create a blank one, and that would satisfy the
| check from then on.
|
| To
Salut Romain,
On 17 April 2009 at 16:36, Romain Francois wrote:
| I agree with the usefulness of having this available, but there is
| absolutely no way people are going to log such information in a
| systematic fashion. In the other hand, if you have version 1 and version
There is: you gentl
On Fri, Apr 17, 2009 at 10:12 AM, Dirk Eddelbuettel wrote:
>
> On 17 April 2009 at 09:05, Duncan Murdoch wrote:
> | That would be a waste of time. People don't use the package
> | documentation schemes that are in place; why would they use a new one?
>
> Because of scattered documentation and lac
On 4/17/2009 10:12 AM, Dirk Eddelbuettel wrote:
On 17 April 2009 at 09:05, Duncan Murdoch wrote:
| That would be a waste of time. People don't use the package
| documentation schemes that are in place; why would they use a new one?
Because of scattered documentation and lack of best practices
Philippe Grosjean wrote:
Hello,
Here are a few questions that would be useful to get an answer via
dedicated functions in utils or tools packages:
- When did function foo appeared in R or in a given package?
- When did argument myarg appeared in function foo?
- When did function bar get deprec
On 17 April 2009 at 09:05, Duncan Murdoch wrote:
| That would be a waste of time. People don't use the package
| documentation schemes that are in place; why would they use a new one?
Because of scattered documentation and lack of best practices? Many things
are possible with R and packages,
On 4/17/2009 9:16 AM, Philippe Grosjean wrote:
Duncan Murdoch wrote:
On 4/17/2009 7:48 AM, ronggui wrote:
2009/4/17 Duncan Murdoch :
[...]
It might be helpful, but often new arguments or changed behaviour happen
later, so you'd really need a full change history for the function:
that's what'
On 4/17/2009 8:47 AM, Christian Ritz wrote:
Hi Duncan,
on a related note: It would be nice to have a function similar to
tools::readNEWS() for
showing package-specific CHANGES/NEWS files (if available).
That would be a waste of time. People don't use the package
documentation schemes that
Duncan Murdoch wrote:
On 4/17/2009 7:48 AM, ronggui wrote:
2009/4/17 Duncan Murdoch :
[...]
It might be helpful, but often new arguments or changed behaviour happen
later, so you'd really need a full change history for the function:
that's what's in the Subversion log, or to some extent, in t
Hi Duncan,
on a related note: It would be nice to have a function similar to
tools::readNEWS() for
showing package-specific CHANGES/NEWS files (if available).
Something like:
"showNews" <- function(pkgname, filename = c("NEWS", "CHANGES"))
{
filename <- match.arg(filename)
file.show(
Thanks -- that looks like a reasonable change. I'll have a more
careful look in the next couple of days and apply if I don't run into
any unexpected issues.
luke
On Thu, 16 Apr 2009, William Dunlap wrote:
A possible fix for this is to filter the 'unsused' list before
printing the error messag
On 4/17/2009 7:48 AM, ronggui wrote:
2009/4/17 Duncan Murdoch :
Philippe Grosjean wrote:
Hello,
Here are a few questions that would be useful to get an answer via
dedicated functions in utils or tools packages:
- When did function foo appeared in R or in a given package?
- When did argument m
2009/4/17 Duncan Murdoch :
> Philippe Grosjean wrote:
>>
>> Hello,
>>
>> Here are a few questions that would be useful to get an answer via
>> dedicated functions in utils or tools packages:
>> - When did function foo appeared in R or in a given package?
>> - When did argument myarg appeared in fun
Philippe Grosjean wrote:
Hello,
Here are a few questions that would be useful to get an answer via
dedicated functions in utils or tools packages:
- When did function foo appeared in R or in a given package?
- When did argument myarg appeared in function foo?
- When did function bar get deprec
Hello,
Here are a few questions that would be useful to get an answer via
dedicated functions in utils or tools packages:
- When did function foo appeared in R or in a given package?
- When did argument myarg appeared in function foo?
- When did function bar get deprecated or when did it disapp
21 matches
Mail list logo
