From couteau at codelutin.com  Wed Dec  2 08:27:14 2009
From: couteau at codelutin.com (Jean Couteau)
Date: Wed, 02 Dec 2009 08:27:14 +0100
Subject: [Rd] Bug in R evaluating a huge instruction (PR#14096)
In-Reply-To: <4B152F22.9000506@stats.uwo.ca>
References: <20091130155010.4EFF1282EFE3@mail.pubhealth.ku.dk>
	<4B144659.6090702@stats.uwo.ca> <4B14AEB1.9090206@codelutin.com>
	<4B152F22.9000506@stats.uwo.ca>
Message-ID: <4B1616D2.70908@codelutin.com>

Thank you very much for your input Duncan and Romain.

I will try to do what you are advising. The R instruction is generated 
from java using jri (and an abstraction layer we built upon it : 
nuiton-j2r), i will try add this limitation to nuiton-j2r so that it 
split the instruction if it is too long.

Best regards,
Jean

Duncan Murdoch wrote:
> On 01/12/2009 12:50 AM, Jean Couteau wrote:
>> Thanks for your time Duncan,
>>
>> I join here the instruction that is not correct, hoping that might 
>> help you. The file is encoded in utf-8 so you should not have any 
>> problem reading it.
>>
>> I doubt to that it is an R bug too, but with all my tests i am less 
>> and less sure of that.
>
> I have no problem sourcing that file, but I do get an error if I try 
> to cut and paste it, because it's a single line of 4890 characters, 
> and that's too long.  So this is an R limitation, but it's one with an 
> easy workaround:  just add some line breaks into your source.
>
> Duncan Murdoch
>
>
>>
>> Best regards,
>> Jean Couteau
>>> Your message has encoding problems, so it's not readable.  Could you 
>>> put the code online somewhere where we could download it in its 
>>> original form?  I doubt if this is an R bug, but I can't point out 
>>> the problem in your code (or confirm that it really is an R bug) 
>>> without an undamaged copy of the code.
>>>
>>> Duncan Murdoch
>>>
>>>
>>>
>>
>
>



[Rd] Bug in R evaluating a huge instruction (PR#14096)
Jean Couteau