date:20171129

Re: [Rd] binary form of is() contradicts its unary form

2017-11-29 Thread Suzen, Mehmet

On 29 November 2017 at 21:45, Hervé Pagès  wrote:
> You're missing the point of my original post. Which is that
> there is a serious inconsistency between the unary and binary
> forms of is(). Maybe the binary form is right in case of

My understanding is that there is no inconsistency. `is` does what it
claims, from the documentation:

‘is’: With two arguments, tests whether ‘object’ can be treated as
  from ‘class2’.

  With one argument, returns all the super-classes of this
  object's class.

Important verb there is 'can be treated as from' with two arguments. So,
one can not treat `data.frame` as from 'list' class in a simple sense,
even though it inherits
from list. The complication is that list is a Primitive and this is
not coming from a
clean S4 hierarchy c.f, your A, B example.

Also, strictly speaking, having super-classes resolved does not
automatically qualify an
assumption that the object can be treated as a class of one of its
super-classes.

Cheers,
Mehmet

__
R-devel@r-project.org mailing list
https://stat.ethz.ch/mailman/listinfo/r-devel

[R-pkg-devel] R package with Swift code

2017-11-29 Thread Guillaume Chapron

Hello,

Does anyone know of an example of a R package that contains Swift code 
(https://swift.org), like many packages use C code?

Thanks

Guillaume
__
R-package-devel@r-project.org mailing list
https://stat.ethz.ch/mailman/listinfo/r-package-devel

Re: [Rd] binary form of is() contradicts its unary form

2017-11-29 Thread Hervé Pagès

Yes, data.frame is not an S4 class but is(data.frame())
finds its super-classes anyway and without the need to wrap
it in asS4(). And "list' is one of the super-classes. Then
is(data.frame(), "list") contradicts this.

I'm not asking for a workaround. I already have one with
'class2 %in% is(object)' as reported in my original post.
'is(asS4(object), class2)' is maybe another one but, unlike
the former, it's not obvious that it will behave consistently
with unary is(). There could be some other surprise on the
way.

You're missing the point of my original post. Which is that
there is a serious inconsistency between the unary and binary
forms of is(). Maybe the binary form is right in case of
is(data.frame(), "list"). But then the unary form should not
return "list'. This inconsistency will potentially hurt anybody
who tries to do computations on a class hierarchy, especially
if the hierarchy is complex and mixes S4 and S3 classes. So I'm
hoping this can be addressed. Hope you understand.

Cheers,
H.

On 11/29/2017 12:21 PM, Suzen, Mehmet wrote:

Hi Herve,

Interesting observation with `setClass` but it is for S4.  It looks
like `data.frame()` is not an S4 class.

isS4(data.frame())

[1] FALSE

And in your case this might help:

is(asS4(data.frame()), "list")

[1] TRUE

Looks like `is` is designed for S4 classes, I am not entirely sure.

Best,
-Mehmet

On 29 November 2017 at 20:46, Hervé Pagès  wrote:

Hi Mehmet,

On 11/29/2017 11:22 AM, Suzen, Mehmet wrote:

Hi Herve,

I think you are confusing subclasses and classes. There is no
contradiction. `is` documentation
is very clear:

`With one argument, returns all the super-classes of this object's class.`

Yes that's indeed very clear. So if "list" is a super-class
of "data.frame" (as reported by is(data.frame())), then
is(data.frame(), "list") should be TRUE.

With S4 classes:

   setClass("A")
   setClass("B", contains="A")

   ## Get all the super-classes of B.
   is(new("B"))
   # [1] "B" "A"

   ## Does a B object inherit from A?
   is(new("B"), "A")
   # [1] TRUE

Cheers,
H.

Note that object class is always `data.frame` here, check:

  > class(data.frame())
[1] "data.frame"
  > is(data.frame(), "data.frame")
[1] TRUE

Best,
Mehmet

On 29 Nov 2017 19:13, "Hervé Pagès" > wrote:

 Hi,

 The unary forms of is() and extends() report that data.frame
 extends list, oldClass, and vector:

> is(data.frame())
[1] "data.frame" "list"   "oldClass"   "vector"

> extends("data.frame")
[1] "data.frame" "list"   "oldClass"   "vector"

 However, the binary form of is() disagrees:

> is(data.frame(), "list")
[1] FALSE
> is(data.frame(), "oldClass")
[1] FALSE
> is(data.frame(), "vector")
[1] FALSE

 while the binary form of extends() agrees:

> extends("data.frame", "list")
[1] TRUE
> extends("data.frame", "oldClass")
[1] TRUE
> extends("data.frame", "vector")
[1] TRUE

 Who is right?

 Shouldn't 'is(object, class2)' be equivalent
 to 'class2 %in% is(object)'? Furthermore, is there
 any reason why 'is(object, class2)' is not implemented
 as 'class2 %in% is(object)'?

 Thanks,
 H.

 --
 Hervé Pagès

 Program in Computational Biology
 Division of Public Health Sciences
 Fred Hutchinson Canc

er
 Research Center
 1100 Fairview Ave. N, M1-B514
 P.O. Box 19024
 Seattle, WA 98109-1024

 E-mail: hpa...@fredhutch.org 
 Phone:  (206) 667-5791
 Fax:(206) 667-1319

 __
 R-devel@r-project.org  mailing list

https://urldefense.proofpoint.com/v2/url?u=https-3A__stat.ethz.ch_mailman_listinfo_r-2Ddevel=DwIFaQ=eRAMFD45gAfqt84VtBcfhQ=BK7q3XeAvimeWdGbWY_wJYbW0WYiZvSXAJJKaaPhzWA=Edo4xQQyNSdlhiJjtVDnOcunTA8a6KT5EN7_jowitP8=ES11eQ8qMdiYMc5X-SbEfQyy2VoX6MUfX0skN-QWunc=

--
Hervé Pagès

Program in Computational Biology
Division of Public Health Sciences
Fred Hutchinson Cancer Research Center
1100 Fairview Ave. N, M1-B514
P.O. Box 19024
Seattle, WA 98109-1024

E-mail: hpa...@fredhutch.org
Phone:  (206) 667-5791
Fax:(206) 667-1319

--
Hervé Pagès

Program in Computational Biology
Division of Public Health Sciences

Re: [Rd] binary form of is() contradicts its unary form

2017-11-29 Thread Suzen, Mehmet

Hi Herve,

Interesting observation with `setClass` but it is for S4.  It looks
like `data.frame()` is not an S4 class.

> isS4(data.frame())
[1] FALSE

And in your case this might help:

> is(asS4(data.frame()), "list")
[1] TRUE

Looks like `is` is designed for S4 classes, I am not entirely sure.

Best,
-Mehmet

On 29 November 2017 at 20:46, Hervé Pagès  wrote:
> Hi Mehmet,
>
> On 11/29/2017 11:22 AM, Suzen, Mehmet wrote:
>>
>> Hi Herve,
>>
>> I think you are confusing subclasses and classes. There is no
>> contradiction. `is` documentation
>> is very clear:
>>
>> `With one argument, returns all the super-classes of this object's class.`
>
>
> Yes that's indeed very clear. So if "list" is a super-class
> of "data.frame" (as reported by is(data.frame())), then
> is(data.frame(), "list") should be TRUE.
>
> With S4 classes:
>
>   setClass("A")
>   setClass("B", contains="A")
>
>   ## Get all the super-classes of B.
>   is(new("B"))
>   # [1] "B" "A"
>
>   ## Does a B object inherit from A?
>   is(new("B"), "A")
>   # [1] TRUE
>
> Cheers,
> H.
>
>>
>> Note that object class is always `data.frame` here, check:
>>
>>  > class(data.frame())
>> [1] "data.frame"
>>  > is(data.frame(), "data.frame")
>> [1] TRUE
>>
>> Best,
>> Mehmet
>>
>>
>>
>>
>>
>> On 29 Nov 2017 19:13, "Hervé Pagès" > > wrote:
>>
>> Hi,
>>
>> The unary forms of is() and extends() report that data.frame
>> extends list, oldClass, and vector:
>>
>>> is(data.frame())
>>[1] "data.frame" "list"   "oldClass"   "vector"
>>
>>> extends("data.frame")
>>[1] "data.frame" "list"   "oldClass"   "vector"
>>
>> However, the binary form of is() disagrees:
>>
>>> is(data.frame(), "list")
>>[1] FALSE
>>> is(data.frame(), "oldClass")
>>[1] FALSE
>>> is(data.frame(), "vector")
>>[1] FALSE
>>
>> while the binary form of extends() agrees:
>>
>>> extends("data.frame", "list")
>>[1] TRUE
>>> extends("data.frame", "oldClass")
>>[1] TRUE
>>> extends("data.frame", "vector")
>>[1] TRUE
>>
>> Who is right?
>>
>> Shouldn't 'is(object, class2)' be equivalent
>> to 'class2 %in% is(object)'? Furthermore, is there
>> any reason why 'is(object, class2)' is not implemented
>> as 'class2 %in% is(object)'?
>>
>> Thanks,
>> H.
>>
>> --
>> Hervé Pagès
>>
>> Program in Computational Biology
>> Division of Public Health Sciences
>> Fred Hutchinson Canc
>>
>> er
>> Research Center
>> 1100 Fairview Ave. N, M1-B514
>> P.O. Box 19024
>> Seattle, WA 98109-1024
>>
>> E-mail: hpa...@fredhutch.org 
>> Phone:  (206) 667-5791
>> Fax:(206) 667-1319
>>
>> __
>> R-devel@r-project.org  mailing list
>> https://stat.ethz.ch/mailman/listinfo/r-devel
>>
>> 
>>
>
> --
> Hervé Pagès
>
> Program in Computational Biology
> Division of Public Health Sciences
> Fred Hutchinson Cancer Research Center
> 1100 Fairview Ave. N, M1-B514
> P.O. Box 19024
> Seattle, WA 98109-1024
>
> E-mail: hpa...@fredhutch.org
> Phone:  (206) 667-5791
> Fax:(206) 667-1319

__
R-devel@r-project.org mailing list
https://stat.ethz.ch/mailman/listinfo/r-devel

Re: [Rd] binary form of is() contradicts its unary form

2017-11-29 Thread Hervé Pagès

Hi Mehmet,

On 11/29/2017 11:22 AM, Suzen, Mehmet wrote:

Hi Herve,

I think you are confusing subclasses and classes. There is no
contradiction. `is` documentation
is very clear:

`With one argument, returns all the super-classes of this object's class.`

Yes that's indeed very clear. So if "list" is a super-class
of "data.frame" (as reported by is(data.frame())), then
is(data.frame(), "list") should be TRUE.

With S4 classes:

  setClass("A")
  setClass("B", contains="A")

  ## Get all the super-classes of B.
  is(new("B"))
  # [1] "B" "A"

  ## Does a B object inherit from A?
  is(new("B"), "A")
  # [1] TRUE

Cheers,
H.

Note that object class is always `data.frame` here, check:

 > class(data.frame())
[1] "data.frame"
 > is(data.frame(), "data.frame")
[1] TRUE

Best,
Mehmet

On 29 Nov 2017 19:13, "Hervé Pagès" > wrote:

Hi,

The unary forms of is() and extends() report that data.frame
extends list, oldClass, and vector:

   > is(data.frame())
   [1] "data.frame" "list"   "oldClass"   "vector"

   > extends("data.frame")
   [1] "data.frame" "list"   "oldClass"   "vector"

However, the binary form of is() disagrees:

   > is(data.frame(), "list")
   [1] FALSE
   > is(data.frame(), "oldClass")
   [1] FALSE
   > is(data.frame(), "vector")
   [1] FALSE

while the binary form of extends() agrees:

   > extends("data.frame", "list")
   [1] TRUE
   > extends("data.frame", "oldClass")
   [1] TRUE
   > extends("data.frame", "vector")
   [1] TRUE

Who is right?

Shouldn't 'is(object, class2)' be equivalent
to 'class2 %in% is(object)'? Furthermore, is there
any reason why 'is(object, class2)' is not implemented
as 'class2 %in% is(object)'?

Thanks,
H.

--
Hervé Pagès

Program in Computational Biology
Division of Public Health Sciences
Fred Hutchinson Canc

er
Research Center
1100 Fairview Ave. N, M1-B514
P.O. Box 19024
Seattle, WA 98109-1024

E-mail: hpa...@fredhutch.org 
Phone:  (206) 667-5791
Fax:(206) 667-1319

__
R-devel@r-project.org  mailing list
https://stat.ethz.ch/mailman/listinfo/r-devel

--
Hervé Pagès

Program in Computational Biology
Division of Public Health Sciences
Fred Hutchinson Cancer Research Center
1100 Fairview Ave. N, M1-B514
P.O. Box 19024
Seattle, WA 98109-1024

E-mail: hpa...@fredhutch.org
Phone:  (206) 667-5791
Fax:(206) 667-1319

__
R-devel@r-project.org mailing list
https://stat.ethz.ch/mailman/listinfo/r-devel

Re: [Rd] binary form of is() contradicts its unary form

2017-11-29 Thread Suzen, Mehmet

Hi Herve,

I think you are confusing subclasses and classes. There is no
contradiction. `is` documentation
is very clear:

`With one argument, returns all the super-classes of this object's class.`

Note that object class is always `data.frame` here, check:

> class(data.frame())
[1] "data.frame"
> is(data.frame(), "data.frame")
[1] TRUE

Best,
Mehmet





On 29 Nov 2017 19:13, "Hervé Pagès"  wrote:

> Hi,
>
> The unary forms of is() and extends() report that data.frame
> extends list, oldClass, and vector:
>
>   > is(data.frame())
>   [1] "data.frame" "list"   "oldClass"   "vector"
>
>   > extends("data.frame")
>   [1] "data.frame" "list"   "oldClass"   "vector"
>
> However, the binary form of is() disagrees:
>
>   > is(data.frame(), "list")
>   [1] FALSE
>   > is(data.frame(), "oldClass")
>   [1] FALSE
>   > is(data.frame(), "vector")
>   [1] FALSE
>
> while the binary form of extends() agrees:
>
>   > extends("data.frame", "list")
>   [1] TRUE
>   > extends("data.frame", "oldClass")
>   [1] TRUE
>   > extends("data.frame", "vector")
>   [1] TRUE
>
> Who is right?
>
> Shouldn't 'is(object, class2)' be equivalent
> to 'class2 %in% is(object)'? Furthermore, is there
> any reason why 'is(object, class2)' is not implemented
> as 'class2 %in% is(object)'?
>
> Thanks,
> H.
>
> --
> Hervé Pagès
>
> Program in Computational Biology
> Division of Public Health Sciences
> Fred Hutchinson Canc
> er
> Research Center
> 1100 Fairview Ave. N, M1-B514
> P.O. Box 19024
> Seattle, WA 98109-1024
>
> E-mail: hpa...@fredhutch.org
> Phone:  (206) 667-5791
> Fax:(206) 667-1319
>
> __
> R-devel@r-project.org mailing list
> https://stat.ethz.ch/mailman/listinfo/r-devel
>

[[alternative HTML version deleted]]

__
R-devel@r-project.org mailing list
https://stat.ethz.ch/mailman/listinfo/r-devel

[Rd] binary form of is() contradicts its unary form

2017-11-29 Thread Hervé Pagès


Hi,

The unary forms of is() and extends() report that data.frame
extends list, oldClass, and vector:

  > is(data.frame())
  [1] "data.frame" "list"   "oldClass"   "vector"

  > extends("data.frame")
  [1] "data.frame" "list"   "oldClass"   "vector"

However, the binary form of is() disagrees:

  > is(data.frame(), "list")
  [1] FALSE
  > is(data.frame(), "oldClass")
  [1] FALSE
  > is(data.frame(), "vector")
  [1] FALSE

while the binary form of extends() agrees:

  > extends("data.frame", "list")
  [1] TRUE
  > extends("data.frame", "oldClass")
  [1] TRUE
  > extends("data.frame", "vector")
  [1] TRUE

Who is right?

Shouldn't 'is(object, class2)' be equivalent
to 'class2 %in% is(object)'? Furthermore, is there
any reason why 'is(object, class2)' is not implemented
as 'class2 %in% is(object)'?

Thanks,
H.

--
Hervé Pagès

Program in Computational Biology
Division of Public Health Sciences
Fred Hutchinson Cancer Research Center
1100 Fairview Ave. N, M1-B514
P.O. Box 19024
Seattle, WA 98109-1024

E-mail: hpa...@fredhutch.org
Phone:  (206) 667-5791
Fax:(206) 667-1319

__
R-devel@r-project.org mailing list
https://stat.ethz.ch/mailman/listinfo/r-devel

Re: [R-pkg-devel] Exited with status -1073741819.

2017-11-29 Thread Marc Schwartz

Rampal,

One additional thought here.

Since you reference RTools in your initial post, I presume that this is 
occurring on Windows, though not sure which version.

Have you tried to build the package using the WinBuilder site provided by Uwe?

If not, go here:

  https://win-builder.r-project.org

and request a build of the package using R-Devel.

See if any warnings/errors are picked up there. If not, then that would seem to 
reinforce the notion that there is something going on locally on your system.

Also, unless I missed it, you did not indicate which version of R-Devel you are 
running or where you obtained it. Did you get it from:

  https://cran.r-project.org/bin/windows/base/rdevel.html

?

Regards,

Marc

> On Nov 29, 2017, at 8:22 AM, Rampal S. Etienne  
> wrote:
> 
> Dear Marc, Martin, Dason,
> 
> I agree that the status number is not very informative, but neither is:
> "Package does not build". The point is that I have no clue what is going
> on, and was just hoping that someone might have seen the exit status
> number before.
> 
> I have done a clean install as suggested but still it won't work with
> R-devel, but it does with R-3.4.2.
> 
> I don't see how my setup is special in any way. It never caused me any
> problems until installing the latest R-devel. What are the changes in
> the latest R-devel that affect the building of packages?
> 
> Cheers, Rampal
> 
> 
> 
> On 29-11-2017 11:16, Martin Maechler wrote:
>>> Rampal S Etienne 
>>>on Wed, 29 Nov 2017 09:19:29 +0100 writes:
>>> Dear Dason,
>>> I don't get this error, but it crashes anyway. 
>> 
>> and you don't show what "crashes" means here.
>> (and yes, Dason is right: The RStudio status number in the
>> 'Subject' is not really useful)
>> 
>>> I've that if I use the
>>> stable version of R (3.4.2) I do NOT get the error anymore, so I assume
>>> there is something wrong with the current R-devel.
>> 
>>> Regards,
>>> Rampal Etienne
>> 
>> OTOH, the CRAN checks of your package run without any problem
>> with all 5 versions of R-devel there :
>> 
>>  https://cran.r-project.org/web/checks/check_results_SADISA.html
>> 
>> so it may rather be something specific to your setup ??
>> 
>> Martin Maechler
>> 
>> 
>>> On 29-11-2017 0:36, Dason Kurkiewicz wrote:
 Do you get the same error if you try to build on the command line
 outside of RStudio?

 On Nov 28, 2017 3:51 PM, "Rampal Etienne" > wrote:

 Dear all,

 I updated RStudio, Rtools and R-devel, and then I tried to build a
 package in RStudio that I had been able to build before without
 any problems. But now I got the following error:

 Updating SADISA documentatiob
 Loading SADISA
 Exited with status -1073741819.

 That's all. What is this exit status? I can still build other
 packages, so it does not happen all the time. I can use "Load all"
 and all functions sseem to work fine.

 Any suggestions?

 Kind regards, Rampal Etienne

__
R-package-devel@r-project.org mailing list
https://stat.ethz.ch/mailman/listinfo/r-package-devel

Re: [R-pkg-devel] Exited with status -1073741819.

2017-11-29 Thread William Dunlap

You wrote
Exited with status -1073741819.

The low byte of that status code is 5, which I think means a segmentation
fault - reading
or writing an address that you do not have permission of use.
  > as.hexmode(-1073741819)
  [1] "c005"
If your code uses memory that it has not allocated it is somewhat random
whether you
get a segmentation fault or not.  'valgrind' can detect such errors more
reliably.  Try that
on a platform where your package builds.


Bill Dunlap
TIBCO Software
wdunlap tibco.com

On Tue, Nov 28, 2017 at 12:51 PM, Rampal Etienne 
wrote:

> Dear all,
>
> I updated RStudio, Rtools and R-devel, and then I tried to build a package
> in RStudio that I had been able to build before without any problems. But
> now I got the following error:
>
> Updating SADISA documentatiob
> Loading SADISA
> Exited with status -1073741819.
>
> That's all. What is this exit status? I can still build other packages, so
> it does not happen all the time. I can use "Load all" and all functions
> sseem to work fine.
>
> Any suggestions?
>
> Kind regards, Rampal Etienne
>
> __
> R-package-devel@r-project.org mailing list
> https://stat.ethz.ch/mailman/listinfo/r-package-devel
>

[[alternative HTML version deleted]]

__
R-package-devel@r-project.org mailing list
https://stat.ethz.ch/mailman/listinfo/r-package-devel

Re: [R-pkg-devel] Exited with status -1073741819.

2017-11-29 Thread Martin Maechler

> Rampal S Etienne 
> on Wed, 29 Nov 2017 14:22:54 +0100 writes:

> Dear Marc, Martin, Dason,
> I agree that the status number is not very informative, but neither is:
> "Package does not build". The point is that I have no clue what is going
> on, and was just hoping that someone might have seen the exit status
> number before.

> I have done a clean install as suggested but still it won't work with
> R-devel, but it does with R-3.4.2.

> I don't see how my setup is special in any way. It never caused me any
> problems until installing the latest R-devel. What are the changes in
> the latest R-devel that affect the building of packages?

1000s of packages are built every day with R-devel, notably on
the machines that produce the CRAN checks, but also in several
if not many other places.

Consequently, it must be *your* problem, notably as your package
does build flawlessly on 5 different CRAN check machines running R-devel.

But of course, the purpose of *this* list (not of R-devel!) is
to help you with this problem,
hence back to what you wrote above:

"Package does not build"  is actually  more useful than a status
   number that looks random (and/or from a large integer overflow ..).

To me it would mean the package does not even build and
therefore *check*ing the package did not even properly start.

As next step (in solving the problem) you should probably learn
to either debug the devtools which you are probably using
[otherwise you would give us more information !],
or---even more useful in the long run---learn to build a package
in the shell (aka "terminal") instead of inside RStudio, because then,
using 'Rcmd build ' would almost surely give you more clues
than just "does not build".


> On 29-11-2017 11:16, Martin Maechler wrote:
>>> Rampal S Etienne 
>>> on Wed, 29 Nov 2017 09:19:29 +0100 writes:
>> > Dear Dason,
>> > I don't get this error, but it crashes anyway. 
>> 
>> and you don't show what "crashes" means here.
>> (and yes, Dason is right: The RStudio status number in the
>> 'Subject' is not really useful)
>> 
>> > I've that if I use the
>> > stable version of R (3.4.2) I do NOT get the error anymore, so I assume
>> > there is something wrong with the current R-devel.
>> 
>> > Regards,
>> > Rampal Etienne
>> 
>> OTOH, the CRAN checks of your package run without any problem
>> with all 5 versions of R-devel there :
>> 
>> https://cran.r-project.org/web/checks/check_results_SADISA.html
>> 
>> so it may rather be something specific to your setup ??
>> 
>> Martin Maechler
>> 
>> 
>> > On 29-11-2017 0:36, Dason Kurkiewicz wrote:
>> >> Do you get the same error if you try to build on the command line
>> >> outside of RStudio?
>> >> 
>> >> On Nov 28, 2017 3:51 PM, "Rampal Etienne" > >> > wrote:
>> >> 
>> >> Dear all,
>> >> 
>> >> I updated RStudio, Rtools and R-devel, and then I tried to build a
>> >> package in RStudio that I had been able to build before without
>> >> any problems. But now I got the following error:
>> >> 
>> >> Updating SADISA documentatiob
>> >> Loading SADISA
>> >> Exited with status -1073741819.
>> >> 
>> >> That's all. What is this exit status? I can still build other
>> >> packages, so it does not happen all the time. I can use "Load all"
>> >> and all functions sseem to work fine.
>> >> 
>> >> Any suggestions?
>> >> 
>> >> Kind regards, Rampal Etienne

__
R-package-devel@r-project.org mailing list
https://stat.ethz.ch/mailman/listinfo/r-package-devel

Re: [Rd] Un-informative Error in re-building vignettes

2017-11-29 Thread Marc Schwartz



> On Nov 29, 2017, at 10:25 AM, Toby Hocking  wrote:
> 
> I am getting the following on CRAN windows and winbuilder
> https://www.r-project.org/nosvn/R.check/r-devel-windows-ix86+x86_64/penaltyLearning-00check.html
> 
> Apparently there is an error in re-building vignettes, but I do not have
> any idea what it is, because all that is listed is three dots (...). Is
> this a bug in R CMD check?
> 
> If not, the only solution I can think of is removing the vignette entirely.
> Any other ideas?
> 
>   - checking re-building of vignette outputs ... [11s] WARNING
>   Error in re-building vignettes:
> ...
>   - checking PDF version of manual ... OK


Hi,

First, generally CRAN package building related issues should be posted to 
R-Package-Devel, not here:

  https://stat.ethz.ch/mailman/listinfo/r-package-devel 


Second, you might want to review the full CRAN build report for your package, 
which reports more information across several builds:

https://cran.r-project.org/web/checks/check_results_penaltyLearning.html 


Regards,

Marc Schwartz



[[alternative HTML version deleted]]

__
R-devel@r-project.org mailing list
https://stat.ethz.ch/mailman/listinfo/r-devel

[Rd] Un-informative Error in re-building vignettes

2017-11-29 Thread Toby Hocking

I am getting the following on CRAN windows and winbuilder
https://www.r-project.org/nosvn/R.check/r-devel-windows-ix86+x86_64/penaltyLearning-00check.html

Apparently there is an error in re-building vignettes, but I do not have
any idea what it is, because all that is listed is three dots (...). Is
this a bug in R CMD check?

If not, the only solution I can think of is removing the vignette entirely.
Any other ideas?

   - checking re-building of vignette outputs ... [11s] WARNING
   Error in re-building vignettes:
 ...
   - checking PDF version of manual ... OK

[[alternative HTML version deleted]]

__
R-devel@r-project.org mailing list
https://stat.ethz.ch/mailman/listinfo/r-devel

Re: [R-pkg-devel] Exited with status -1073741819.

2017-11-29 Thread Rampal S. Etienne

Dear Marc, Martin, Dason,

I agree that the status number is not very informative, but neither is:
"Package does not build". The point is that I have no clue what is going
on, and was just hoping that someone might have seen the exit status
number before.

I have done a clean install as suggested but still it won't work with
R-devel, but it does with R-3.4.2.

I don't see how my setup is special in any way. It never caused me any
problems until installing the latest R-devel. What are the changes in
the latest R-devel that affect the building of packages?

Cheers, Rampal



On 29-11-2017 11:16, Martin Maechler wrote:
>> Rampal S Etienne 
>> on Wed, 29 Nov 2017 09:19:29 +0100 writes:
> > Dear Dason,
> > I don't get this error, but it crashes anyway. 
>
> and you don't show what "crashes" means here.
> (and yes, Dason is right: The RStudio status number in the
> 'Subject' is not really useful)
>
> > I've that if I use the
> > stable version of R (3.4.2) I do NOT get the error anymore, so I assume
> > there is something wrong with the current R-devel.
>
> > Regards,
> > Rampal Etienne
>
> OTOH, the CRAN checks of your package run without any problem
> with all 5 versions of R-devel there :
>
>   https://cran.r-project.org/web/checks/check_results_SADISA.html
>
> so it may rather be something specific to your setup ??
>
> Martin Maechler
>
>
> > On 29-11-2017 0:36, Dason Kurkiewicz wrote:
> >> Do you get the same error if you try to build on the command line
> >> outside of RStudio?
> >> 
> >> On Nov 28, 2017 3:51 PM, "Rampal Etienne"  >> > wrote:
> >> 
> >> Dear all,
> >> 
> >> I updated RStudio, Rtools and R-devel, and then I tried to build a
> >> package in RStudio that I had been able to build before without
> >> any problems. But now I got the following error:
> >> 
> >> Updating SADISA documentatiob
> >> Loading SADISA
> >> Exited with status -1073741819.
> >> 
> >> That's all. What is this exit status? I can still build other
> >> packages, so it does not happen all the time. I can use "Load all"
> >> and all functions sseem to work fine.
> >> 
> >> Any suggestions?
> >> 
> >> Kind regards, Rampal Etienne
> >> 
> >> __
> >> R-package-devel@r-project.org
> >>  mailing list
> >> https://stat.ethz.ch/mailman/listinfo/r-package-devel
> >> 
> >> 
>
>
> > [[alternative HTML version deleted]]
>
> > __
> > R-package-devel@r-project.org mailing list
> > https://stat.ethz.ch/mailman/listinfo/r-package-devel

__
R-package-devel@r-project.org mailing list
https://stat.ethz.ch/mailman/listinfo/r-package-devel

Re: [R-pkg-devel] Exited with status -1073741819.

2017-11-29 Thread Martin Maechler

> Rampal S Etienne 
> on Wed, 29 Nov 2017 09:19:29 +0100 writes:

> Dear Dason,
> I don't get this error, but it crashes anyway. 

and you don't show what "crashes" means here.
(and yes, Dason is right: The RStudio status number in the
'Subject' is not really useful)

> I've that if I use the
> stable version of R (3.4.2) I do NOT get the error anymore, so I assume
> there is something wrong with the current R-devel.

> Regards,
> Rampal Etienne

OTOH, the CRAN checks of your package run without any problem
with all 5 versions of R-devel there :

  https://cran.r-project.org/web/checks/check_results_SADISA.html

so it may rather be something specific to your setup ??

Martin Maechler


> On 29-11-2017 0:36, Dason Kurkiewicz wrote:
>> Do you get the same error if you try to build on the command line
>> outside of RStudio?
>> 
>> On Nov 28, 2017 3:51 PM, "Rampal Etienne" > > wrote:
>> 
>> Dear all,
>> 
>> I updated RStudio, Rtools and R-devel, and then I tried to build a
>> package in RStudio that I had been able to build before without
>> any problems. But now I got the following error:
>> 
>> Updating SADISA documentatiob
>> Loading SADISA
>> Exited with status -1073741819.
>> 
>> That's all. What is this exit status? I can still build other
>> packages, so it does not happen all the time. I can use "Load all"
>> and all functions sseem to work fine.
>> 
>> Any suggestions?
>> 
>> Kind regards, Rampal Etienne
>> 
>> __
>> R-package-devel@r-project.org
>>  mailing list
>> https://stat.ethz.ch/mailman/listinfo/r-package-devel
>> 
>> 


> [[alternative HTML version deleted]]

> __
> R-package-devel@r-project.org mailing list
> https://stat.ethz.ch/mailman/listinfo/r-package-devel

__
R-package-devel@r-project.org mailing list
https://stat.ethz.ch/mailman/listinfo/r-package-devel

Re: [R-pkg-devel] Exited with status -1073741819.

2017-11-29 Thread Rampal S. Etienne

Dear Dason,

I don't get this error, but it crashes anyway. I've that if I use the
stable version of R (3.4.2) I do NOT get the error anymore, so I assume
there is something wrong with the current R-devel.

Regards,

Rampal Etienne


On 29-11-2017 0:36, Dason Kurkiewicz wrote:
> Do you get the same error if you try to build on the command line
> outside of RStudio?
>
> On Nov 28, 2017 3:51 PM, "Rampal Etienne"  > wrote:
>
> Dear all,
>
> I updated RStudio, Rtools and R-devel, and then I tried to build a
> package in RStudio that I had been able to build before without
> any problems. But now I got the following error:
>
> Updating SADISA documentatiob
> Loading SADISA
> Exited with status -1073741819.
>
> That's all. What is this exit status? I can still build other
> packages, so it does not happen all the time. I can use "Load all"
> and all functions sseem to work fine.
>
> Any suggestions?
>
> Kind regards, Rampal Etienne
>
> __
> R-package-devel@r-project.org
>  mailing list
> https://stat.ethz.ch/mailman/listinfo/r-package-devel
> 
>


[[alternative HTML version deleted]]

__
R-package-devel@r-project.org mailing list
https://stat.ethz.ch/mailman/listinfo/r-package-devel

Re: [Rd] binary form of is() contradicts its unary form

[R-pkg-devel] R package with Swift code

Re: [Rd] binary form of is() contradicts its unary form

Re: [Rd] binary form of is() contradicts its unary form

Re: [Rd] binary form of is() contradicts its unary form

Re: [Rd] binary form of is() contradicts its unary form

[Rd] binary form of is() contradicts its unary form

Re: [R-pkg-devel] Exited with status -1073741819.

Re: [R-pkg-devel] Exited with status -1073741819.

Re: [R-pkg-devel] Exited with status -1073741819.

Re: [Rd] Un-informative Error in re-building vignettes

[Rd] Un-informative Error in re-building vignettes

Re: [R-pkg-devel] Exited with status -1073741819.

Re: [R-pkg-devel] Exited with status -1073741819.

Re: [R-pkg-devel] Exited with status -1073741819.

15 matches

Site Navigation

Mail list logo

Footer information