From vakili.kaveh.email at gmail.com  Tue Nov  4 22:03:24 2014
From: vakili.kaveh.email at gmail.com (kaveh)
Date: Tue, 04 Nov 2014 22:03:24 +0100
Subject: [Rd] Linking to the BH package introduces CRAN warnings
In-Reply-To: <3C0BCB13-BD36-49FE-90E0-C71335B38258@r-enthusiasts.com>
References: <5458D68D.3070102@gmail.com>
	<21592.58816.359652.109459@max.nulle.part>
	<0CDE01C7-C290-4CB8-A1ED-B2A8816CBA49@r-enthusiasts.com>
	<54593CA5.2030002@gmail.com>
	<3C0BCB13-BD36-49FE-90E0-C71335B38258@r-enthusiasts.com>
Message-ID: <54593F1C.3020107@gmail.com>

Dear Romain,


Thanks for all these info,


I will ponder this versus using
some of the alternatives in the R sources


Best regards,

On 2014-11-04 22:01, Romain Fran?ois wrote:
>
>> Le 4 nov. 2014 ? 21:52, kaveh <vakili.kaveh.email at gmail.com 
>> <mailto:vakili.kaveh.email at gmail.com>> a ?crit :
>>
>>
>> Dear Romain,
>>
>>
>>
>>                 /You?re kind of out of luck. These functions are both:
>>                   - used by the boost headers
>>                   - forbidden by R, well at least forbidden by CRAN
>>                 /
>>
>> //
>>
>> Thanks for conforming my earlier fears. Since I only use
>> this header and would like my package to eventually be
>> on CRAN, I was thinking of bypassing BH and just putting
>> these headers in the /inst directory and modifying them
>> to remove the offending calls. I was wondering what your
>> view on this is. Or perhaps there is a simpler alternative?
>>
>> Thanks in advance,
>
> If you go through the hoops of modifying these headers to fulfill R?s 
> requirements, I?m sure it would be of interest to others if you 
> contribute these back to BH.
>
> The danger obviously is that this gets out of sync with boost, which 
> would create work for merging your changes to new boost files from the 
> future.
>
> Some parts of boost (e.g. uBlas) have macros to control whether or not 
> std::cerr is used at all. 
> https://github.com/eddelbuettel/bh/blob/cb1427c27dc068c8328fd1d2f4b1b8a8da1957c2/inst/include/boost/numeric/ublas/exception.hpp#L215
>
> But I don?t think this is of any relevance to the files you want to use.
>
> Romain
>
>> On 2014-11-04 21:46, Romain Fran?ois wrote:
>>>> Le 4 nov. 2014 ? 15:42, Dirk Eddelbuettel<edd at debian.org>  a ?crit :
>>>>
>>>>
>>>> On 4 November 2014 at 14:37, kaveh wrote:
>>>> | Dear all,
>>>> |
>>>> | I'm working on a project that links to the BH package
>>>> | (http://cran.r-project.org/web/packages/BH/index.html).
>>>> |
>>>> | My packages doesn't call entry points which might terminate R nor
>>>> | write to stdout/stderr instead of to the console.
>>>> |
>>>> | However, it seems some of the codes in the BH package
>>>> | might. At any rate, when I include some boost headers such as
>>>> | boost/math/distributions/ through BH, I get the following warnings
>>>> |   when  submitting to the win-builder page:
>>>> |
>>>> |
>>>> |    Found '_ZSt4cerr', possibly from 'std::cerr' (C++)
>>>> |
>>>> |    Found 'abort', possibly from 'abort' (C), 'runtime' (Fortran)
>>>> |
>>>> |    Found '_ZSt4cerr', possibly from 'std::cerr' (C++)
>>>> |
>>>> |    Found 'abort', possibly from 'abort' (C), 'runtime' (Fortran)
>>> You?re kind of out of luck. These functions are both:
>>>   - used by the boost headers
>>>   - forbidden by R, well at least forbidden by CRAN
>>>
>>
>


	[[alternative HTML version deleted]]



[Rd] Linking to the BH package introduces CRAN warnings
kaveh