On Mon, Aug 16, 2010 at 7:10 PM, Jean-Louis Faucher
wrote:
> Thanks Rick
>
> That's more clear now... one more question :-)
> When creating a RexxString instance using new_string, there is no behaviour
> associated to the instance, right ? If I'm not wrong, only newRexx attach a
> behaviour.
> So
Thanks Rick
That's more clear now... one more question :-)
When creating a RexxString instance using new_string, there is no behaviour
associated to the instance, right ? If I'm not wrong, only newRexx attach a
behaviour.
So this instance created by new_string can be used internally, by calling
di
On Mon, Aug 16, 2010 at 5:48 PM, Jean-Louis Faucher
wrote:
> Hi,
>
> I saw those lines in RexxArray::toString :
> RexxMutableBuffer *mutbuffer = ((RexxMutableBufferClass*)
> TheMutableBufferClass)->newRexx(NULL, 0);
> ProtectedObject p1(mutbuffer);
> mutbuffer->append(_stringValue);
> newString =
Hi,
I saw those lines in RexxArray::toString :
RexxMutableBuffer *mutbuffer = ((RexxMutableBufferClass*)
TheMutableBufferClass)->newRexx(NULL, 0);
ProtectedObject p1(mutbuffer);
mutbuffer->append(_stringValue);
newString = mutbuffer->makeString();
Q1 :
I don't understand the implementation of Rex
On 16.08.2010 20:38, David Ashley wrote:
> Right now the build machine is in a sort of transition state. All the
> nightly
> builds are running (with the exception of Win XP) but I need to install a new
> network card in the new machine before I can start giving access to VMs. I
> should hav
O.K., here is one more piece of information which may be helpful.
Running one of those Rexx programs that cause that error this way from
rexxtry.rex fails:
call testOOo.rxo
whereas the following works:
cmd="rexx testOOo.rxo"
say cmd
cmd
Here are additional variations of invoki
Right now the build machine is in a sort of transition state. All the nightly
builds are running (with the exception of Win XP) but I need to install a new
network card in the new machine before I can start giving access to VMs. I
should have the card this week sometime.
What version of Ubunt
Hmmm, taking a quick look at the code and the places where the file
unreadable error can be triggered, I found the following lines in
FileSystem.cpp:
RexxBuffer *SystemInterpreter::readProgram(const char *file_name)
/***/
/* Function
On 16.08.2010 19:27, Mike Cowlishaw wrote:
>> I might take a look at this, this weekend, if I have time.
>> Unfortunately, the set up required is a deterrring factor.
>>
> This would seem to be an excellent example of the use of a virtual machine
> ... with a standard virtual machine with Ub
Hi Mark,
On 16.08.2010 19:02, Mark Miesfeld wrote:
> I know how frustrating these types of things can be. (But, it is very
> satisfying if you solve them.)
>
Indeed, at the moment it is "superfrustrating", probably because I am a
little bit "outworn" working for weeks now on overhauling the
in
>>> On 8/11/2010 at 04:12 PM, in message
>>> <4c62a1a6022400055...@novprvlin0050.provo.novell.com>, "Erico Mendonca"
>>> wrote:
BUT, I'm getting error on TEST_006 on SLES 11SP1 if I try to use the same build
as SLES 11:
Okay, apparently the test was failing because the networking on
> I might take a look at this, this weekend, if I have time.
> Unfortunately, the set up required is a deterrring factor.
This would seem to be an excellent example of the use of a virtual machine
... with a standard virtual machine with Ubuntu on it, Rony could do the
minimum setup (added packa
Hi Rony,
I know how frustrating these types of things can be. (But, it is very
satisfying if you solve them.)
I might take a look at this, this weekend, if I have time.
Unfortunately, the set up required is a deterrring factor.
Until then:
I would try with a build from trunk. David has the bu
... cut ...
> This would be needed to recreate the problem as I have been facing it:
>
> * get Ubuntu,
> * uninstall the Ubuntu-OOo via synaptic manager (they tamper with
> the genuine OpenOffice, unfortunately, harming the Java
> interface to OOo, which is exploited by BSF4ooR
Hi there,
after experimenting the whole day, I have not yet come to a conclusion
about the cause of a runtime problem I have been experiencing with
ooRexx 4.0.1 on 32- and 64-bit Ubuntu:
* when requiring "UNO.CLS" which requires other Rexx packages
itself, an error along the following l
15 matches
Mail list logo
