On 4 February 2008 at 01:51, Joe Bloggs wrote:
| Dirk Eddelbuettel <[EMAIL PROTECTED]> writes:
|
| > On 3 February 2008 at 01:08, Joe Bloggs wrote:
| > | I am using gdb to debug a c++ library I made for R using Rcpp.
| > | However, when I step through the code it seems to go all over the place,
Dirk Eddelbuettel <[EMAIL PROTECTED]> writes:
> On 3 February 2008 at 01:08, Joe Bloggs wrote:
> | I am using gdb to debug a c++ library I made for R using Rcpp.
> | However, when I step through the code it seems to go all over the place,
> and some of the variables have been optimized out so I c
On Sun, 3 Feb 2008, John Fox wrote:
> Dear Brian,
>
> Are there many primitives that take more than one argument?
Quite a few: see the list in the 'R Internals' manual. But most involve
'...' .
> I see, for example, that round() is another. Might it not be a good idea
> to provide a warning i
On 3 February 2008 at 01:08, Joe Bloggs wrote:
| I am using gdb to debug a c++ library I made for R using Rcpp.
| However, when I step through the code it seems to go all over the place, and
some of the variables have been optimized out so I can't see their values.
| How can I compile without opt
Dear Brian,
Are there many primitives that take more than one argument? I see, for
example, that round() is another. Might it not be a good idea to provide a
warning in the help file(s) that arguments must be supplied in the correct
order?
Regards,
John
> -Original Message-
> From: [EM
Dear Brian,
Are there many primitives that take more than one argument? I see, for
example, that round() is another. Might it not be a good idea to provide a
warning in the help file(s) that arguments must be supplied in the correct
order?
Regards,
John
> -Original Message-
> From: [EM
