I have found the following generics which your function did not inlcude.1]
"as.character.default" "as.expression.default" "as.list.default"
"as.name" [5] "as.pairlist" "as.single.default"
"as.symbol" "body<-" [9] "kronecker" I used the
fol
This is completely out of context,
(and mailman needs to "munge" your sender e-mail because of
unpleasant DMARC stuff),
> edson bastos via R-devel
> on Thu, 4 Jun 2015 05:13:55 -0700 writes:
> I have found the following generics which your function did not inlcude.1]
> "as.c
FWIW (and a bit late in the discussion, I know), I for one do not care
about having NEWS in md format at all.
The solution the Yihui uses (linking to GH from NEWS.Rd) is really annoying
for people with no direct Internet access. For example, I work at an
institute that handles a lot of private dat
Mark,
With respect I think you're conflating two different things here.
I completely agree with you that the workflow Yihui uses where the NEWS
file doesn't actually have the NEWS in it in a form that R can understand
is quite bad for users. It also makes the NEWS difficult to compute on,
which h
Mark,
You're conflating issues here andTwo things I think you are missing:
1. Markdown was designed to be as readable as possible in plain text format
(i.e. the sources, not the rendered file). There's nothing stopping you
reading and parsing a NEWS.md in your head trivially.
2. The proposal her
On 04/06/2015 11:05 AM, Mark van der Loo wrote:
FWIW (and a bit late in the discussion, I know), I for one do not care
about having NEWS in md format at all.
The solution the Yihui uses (linking to GH from NEWS.Rd) is really annoying
for people with no direct Internet access. For example, I work
On 04/06/2015 17:00, Gavin Simpson wrote:
...
1. Markdown was designed to be as readable as possible in plain text format
(i.e. the sources, not the rendered file). There's nothing stopping you
reading and parsing a NEWS.md in your head trivially.
...
That claim is made frequently, but it is no
On 04/06/2015 1:09 PM, Prof Brian Ripley wrote:
On 04/06/2015 17:00, Gavin Simpson wrote:
...
> 1. Markdown was designed to be as readable as possible in plain text format
> (i.e. the sources, not the rendered file). There's nothing stopping you
> reading and parsing a NEWS.md in your head trivia
Agreed, and "There's nothing stopping you reading and parsing a NEWS.md in
your head trivially." was very poorly phrased on my part. Just because I
can filter this out doesn't mean it is easy for others to do so.
Clearly anything with markup, even as light as markdown can be, is not as
simple as p
On 4 June 2015 at 11:16, Duncan Murdoch wrote:
> On 04/06/2015 1:09 PM, Prof Brian Ripley wrote:
>
>> On 04/06/2015 17:00, Gavin Simpson wrote:
>> ...
>> > 1. Markdown was designed to be as readable as possible in plain text
>> format
>> > (i.e. the sources, not the rendered file). There's nothin
On 03/06/2015 08:48, bstr wrote:
Hi all,
I have a C function, say Cfun, that calls Lapack's DGEMM routine and I need
to create a shared library to use Cfun inside R. The C file is the following
#include
#include
#include
void Cfun(double *res, double *X, int *n, int *q)
{
char *ptr_TR
@Gavin: My aim was to point out that the ability to mix developer-facing
documentation with user-facing documentation is not a good reason to want
to support md.
I agree with Duncan that links to within a package would be useful (not
sure if NEWS.Rd supports this).
I'm not so convinced that packa
12 matches
Mail list logo
