[PATCH] Demonstrate failing rtstring ctor

Submitted by snrkiwi on Tue, 2010-09-21 00:56

Attached patches add a test to OCL v1 to create rtstring instances in scripting. The test fails to use rtstring ctor, and instead attempts to create a string (ie std::string) first and then create rstring from that. This is bad.

I can't figure out what the problem is, and hope someone can shed some light.

Test implementation based on rtt/tests/state_test.cpp

Peter, this is based on the plugins/rtalloc that you pulled from my github into rtt-2.0-mainline sometime ago. But as that isn't in v1 nor v2 masters, I can only give you a test that works on my github repo. I can't base it on anything from your git* AFAICT.

Cheers
Stephen

AttachmentSize
0001-plugins-rtalloc-Add-test-case-demonstrating-failing-.patch15.67 KB
0002-plugins-rtalloc-Preliminary-implementation-of-rtstri.patch3.06 KB
‹ [PATCH] typekit: move serialization code in separate header Linking typelib ›
»

[PATCH] Demonstrate failing rtstring ctor

Submitted by snrkiwi on Fri, 2010-10-22 03:32.

On Oct 18, 2010, at 11:23 , Peter Soetens wrote:

> On Tuesday 21 September 2010 13:19:15 Stephen Roderick wrote:
>> On Sep 21, 2010, at 03:26 , Peter Soetens wrote:
>>> On Tuesday 21 September 2010 02:55:22 S Roderick wrote:
>>>> Attached patches add a test to OCL v1 to create rtstring instances in
>>>> scripting. The test fails to use rtstring ctor, and instead attempts to
>>>> create a string (ie std::string) first and then create rstring from
>>>> that. This is bad.
>>>
>>> That's probably because std::string is hardcoded in the parsers, and it
>>> assumes every char* is going into a datasource of std::string. The only
>>> solution seems to be to pass it as a char* into a registered constructor
>>> for rt_string if a user writes it like this : rt_string("foo"), just
>>> like in C++.
>>
>> My test case has an example exactly like that, I believe. It fails.
>
> Could you add this as a bug report ? I'll loose track of it otherwise...
>
> Thanks,
>
> Peter

np

https://www.fmtc.be/bugzilla/orocos/show_bug.cgi?id=789

»

[PATCH] Demonstrate failing rtstring ctor

Submitted by snrkiwi on Fri, 2010-10-22 02:52.

On Oct 18, 2010, at 11:23 , Peter Soetens wrote:

> On Tuesday 21 September 2010 13:19:15 Stephen Roderick wrote:
>> On Sep 21, 2010, at 03:26 , Peter Soetens wrote:
>>> On Tuesday 21 September 2010 02:55:22 S Roderick wrote:
>>>> Attached patches add a test to OCL v1 to create rtstring instances in
>>>> scripting. The test fails to use rtstring ctor, and instead attempts to
>>>> create a string (ie std::string) first and then create rstring from
>>>> that. This is bad.
>>>
>>> That's probably because std::string is hardcoded in the parsers, and it
>>> assumes every char* is going into a datasource of std::string. The only
>>> solution seems to be to pass it as a char* into a registered constructor
>>> for rt_string if a user writes it like this : rt_string("foo"), just
>>> like in C++.
>>
>> My test case has an example exactly like that, I believe. It fails.
>
> Could you add this as a bug report ? I'll loose track of it otherwise...
>
> Thanks,
>
> Peter

np

https://www.fmtc.be/bugzilla/orocos/show_bug.cgi?id=789

»

[PATCH] Demonstrate failing rtstring ctor

Submitted by snrkiwi on Fri, 2010-10-22 02:12.

On Oct 18, 2010, at 11:23 , Peter Soetens wrote:

> On Tuesday 21 September 2010 13:19:15 Stephen Roderick wrote:
>> On Sep 21, 2010, at 03:26 , Peter Soetens wrote:
>>> On Tuesday 21 September 2010 02:55:22 S Roderick wrote:
>>>> Attached patches add a test to OCL v1 to create rtstring instances in
>>>> scripting. The test fails to use rtstring ctor, and instead attempts to
>>>> create a string (ie std::string) first and then create rstring from
>>>> that. This is bad.
>>>
>>> That's probably because std::string is hardcoded in the parsers, and it
>>> assumes every char* is going into a datasource of std::string. The only
>>> solution seems to be to pass it as a char* into a registered constructor
>>> for rt_string if a user writes it like this : rt_string("foo"), just
>>> like in C++.
>>
>> My test case has an example exactly like that, I believe. It fails.
>
> Could you add this as a bug report ? I'll loose track of it otherwise...
>
> Thanks,
>
> Peter

np

https://www.fmtc.be/bugzilla/orocos/show_bug.cgi?id=789

»

[PATCH] Demonstrate failing rtstring ctor

Submitted by snrkiwi on Fri, 2010-10-22 01:32.

On Oct 18, 2010, at 11:23 , Peter Soetens wrote:

> On Tuesday 21 September 2010 13:19:15 Stephen Roderick wrote:
>> On Sep 21, 2010, at 03:26 , Peter Soetens wrote:
>>> On Tuesday 21 September 2010 02:55:22 S Roderick wrote:
>>>> Attached patches add a test to OCL v1 to create rtstring instances in
>>>> scripting. The test fails to use rtstring ctor, and instead attempts to
>>>> create a string (ie std::string) first and then create rstring from
>>>> that. This is bad.
>>>
>>> That's probably because std::string is hardcoded in the parsers, and it
>>> assumes every char* is going into a datasource of std::string. The only
>>> solution seems to be to pass it as a char* into a registered constructor
>>> for rt_string if a user writes it like this : rt_string("foo"), just
>>> like in C++.
>>
>> My test case has an example exactly like that, I believe. It fails.
>
> Could you add this as a bug report ? I'll loose track of it otherwise...
>
> Thanks,
>
> Peter

np

https://www.fmtc.be/bugzilla/orocos/show_bug.cgi?id=789

»

[PATCH] Demonstrate failing rtstring ctor

Submitted by snrkiwi on Fri, 2010-10-22 00:52.

On Oct 18, 2010, at 11:23 , Peter Soetens wrote:

> On Tuesday 21 September 2010 13:19:15 Stephen Roderick wrote:
>> On Sep 21, 2010, at 03:26 , Peter Soetens wrote:
>>> On Tuesday 21 September 2010 02:55:22 S Roderick wrote:
>>>> Attached patches add a test to OCL v1 to create rtstring instances in
>>>> scripting. The test fails to use rtstring ctor, and instead attempts to
>>>> create a string (ie std::string) first and then create rstring from
>>>> that. This is bad.
>>>
>>> That's probably because std::string is hardcoded in the parsers, and it
>>> assumes every char* is going into a datasource of std::string. The only
>>> solution seems to be to pass it as a char* into a registered constructor
>>> for rt_string if a user writes it like this : rt_string("foo"), just
>>> like in C++.
>>
>> My test case has an example exactly like that, I believe. It fails.
>
> Could you add this as a bug report ? I'll loose track of it otherwise...
>
> Thanks,
>
> Peter

np

https://www.fmtc.be/bugzilla/orocos/show_bug.cgi?id=789

»

[PATCH] Demonstrate failing rtstring ctor

Submitted by snrkiwi on Fri, 2010-10-22 00:12.

On Oct 18, 2010, at 11:23 , Peter Soetens wrote:

> On Tuesday 21 September 2010 13:19:15 Stephen Roderick wrote:
>> On Sep 21, 2010, at 03:26 , Peter Soetens wrote:
>>> On Tuesday 21 September 2010 02:55:22 S Roderick wrote:
>>>> Attached patches add a test to OCL v1 to create rtstring instances in
>>>> scripting. The test fails to use rtstring ctor, and instead attempts to
>>>> create a string (ie std::string) first and then create rstring from
>>>> that. This is bad.
>>>
>>> That's probably because std::string is hardcoded in the parsers, and it
>>> assumes every char* is going into a datasource of std::string. The only
>>> solution seems to be to pass it as a char* into a registered constructor
>>> for rt_string if a user writes it like this : rt_string("foo"), just
>>> like in C++.
>>
>> My test case has an example exactly like that, I believe. It fails.
>
> Could you add this as a bug report ? I'll loose track of it otherwise...
>
> Thanks,
>
> Peter

np

https://www.fmtc.be/bugzilla/orocos/show_bug.cgi?id=789

»

[PATCH] Demonstrate failing rtstring ctor

Submitted by snrkiwi on Thu, 2010-10-21 23:32.

On Oct 18, 2010, at 11:23 , Peter Soetens wrote:

> On Tuesday 21 September 2010 13:19:15 Stephen Roderick wrote:
>> On Sep 21, 2010, at 03:26 , Peter Soetens wrote:
>>> On Tuesday 21 September 2010 02:55:22 S Roderick wrote:
>>>> Attached patches add a test to OCL v1 to create rtstring instances in
>>>> scripting. The test fails to use rtstring ctor, and instead attempts to
>>>> create a string (ie std::string) first and then create rstring from
>>>> that. This is bad.
>>>
>>> That's probably because std::string is hardcoded in the parsers, and it
>>> assumes every char* is going into a datasource of std::string. The only
>>> solution seems to be to pass it as a char* into a registered constructor
>>> for rt_string if a user writes it like this : rt_string("foo"), just
>>> like in C++.
>>
>> My test case has an example exactly like that, I believe. It fails.
>
> Could you add this as a bug report ? I'll loose track of it otherwise...
>
> Thanks,
>
> Peter

np

https://www.fmtc.be/bugzilla/orocos/show_bug.cgi?id=789

»

[PATCH] Demonstrate failing rtstring ctor

Submitted by snrkiwi on Thu, 2010-10-21 22:52.

On Oct 18, 2010, at 11:23 , Peter Soetens wrote:

> On Tuesday 21 September 2010 13:19:15 Stephen Roderick wrote:
>> On Sep 21, 2010, at 03:26 , Peter Soetens wrote:
>>> On Tuesday 21 September 2010 02:55:22 S Roderick wrote:
>>>> Attached patches add a test to OCL v1 to create rtstring instances in
>>>> scripting. The test fails to use rtstring ctor, and instead attempts to
>>>> create a string (ie std::string) first and then create rstring from
>>>> that. This is bad.
>>>
>>> That's probably because std::string is hardcoded in the parsers, and it
>>> assumes every char* is going into a datasource of std::string. The only
>>> solution seems to be to pass it as a char* into a registered constructor
>>> for rt_string if a user writes it like this : rt_string("foo"), just
>>> like in C++.
>>
>> My test case has an example exactly like that, I believe. It fails.
>
> Could you add this as a bug report ? I'll loose track of it otherwise...
>
> Thanks,
>
> Peter

np

https://www.fmtc.be/bugzilla/orocos/show_bug.cgi?id=789

»

[PATCH] Demonstrate failing rtstring ctor

Submitted by snrkiwi on Thu, 2010-10-21 22:12.

On Oct 18, 2010, at 11:23 , Peter Soetens wrote:

> On Tuesday 21 September 2010 13:19:15 Stephen Roderick wrote:
>> On Sep 21, 2010, at 03:26 , Peter Soetens wrote:
>>> On Tuesday 21 September 2010 02:55:22 S Roderick wrote:
>>>> Attached patches add a test to OCL v1 to create rtstring instances in
>>>> scripting. The test fails to use rtstring ctor, and instead attempts to
>>>> create a string (ie std::string) first and then create rstring from
>>>> that. This is bad.
>>>
>>> That's probably because std::string is hardcoded in the parsers, and it
>>> assumes every char* is going into a datasource of std::string. The only
>>> solution seems to be to pass it as a char* into a registered constructor
>>> for rt_string if a user writes it like this : rt_string("foo"), just
>>> like in C++.
>>
>> My test case has an example exactly like that, I believe. It fails.
>
> Could you add this as a bug report ? I'll loose track of it otherwise...
>
> Thanks,
>
> Peter

np

https://www.fmtc.be/bugzilla/orocos/show_bug.cgi?id=789

»

[PATCH] Demonstrate failing rtstring ctor

Submitted by snrkiwi on Thu, 2010-10-21 21:32.

On Oct 18, 2010, at 11:23 , Peter Soetens wrote:

> On Tuesday 21 September 2010 13:19:15 Stephen Roderick wrote:
>> On Sep 21, 2010, at 03:26 , Peter Soetens wrote:
>>> On Tuesday 21 September 2010 02:55:22 S Roderick wrote:
>>>> Attached patches add a test to OCL v1 to create rtstring instances in
>>>> scripting. The test fails to use rtstring ctor, and instead attempts to
>>>> create a string (ie std::string) first and then create rstring from
>>>> that. This is bad.
>>>
>>> That's probably because std::string is hardcoded in the parsers, and it
>>> assumes every char* is going into a datasource of std::string. The only
>>> solution seems to be to pass it as a char* into a registered constructor
>>> for rt_string if a user writes it like this : rt_string("foo"), just
>>> like in C++.
>>
>> My test case has an example exactly like that, I believe. It fails.
>
> Could you add this as a bug report ? I'll loose track of it otherwise...
>
> Thanks,
>
> Peter

np

https://www.fmtc.be/bugzilla/orocos/show_bug.cgi?id=789

»

[PATCH] Demonstrate failing rtstring ctor

Submitted by snrkiwi on Thu, 2010-10-21 20:52.

On Oct 18, 2010, at 11:23 , Peter Soetens wrote:

> On Tuesday 21 September 2010 13:19:15 Stephen Roderick wrote:
>> On Sep 21, 2010, at 03:26 , Peter Soetens wrote:
>>> On Tuesday 21 September 2010 02:55:22 S Roderick wrote:
>>>> Attached patches add a test to OCL v1 to create rtstring instances in
>>>> scripting. The test fails to use rtstring ctor, and instead attempts to
>>>> create a string (ie std::string) first and then create rstring from
>>>> that. This is bad.
>>>
>>> That's probably because std::string is hardcoded in the parsers, and it
>>> assumes every char* is going into a datasource of std::string. The only
>>> solution seems to be to pass it as a char* into a registered constructor
>>> for rt_string if a user writes it like this : rt_string("foo"), just
>>> like in C++.
>>
>> My test case has an example exactly like that, I believe. It fails.
>
> Could you add this as a bug report ? I'll loose track of it otherwise...
>
> Thanks,
>
> Peter

np

https://www.fmtc.be/bugzilla/orocos/show_bug.cgi?id=789

»

[PATCH] Demonstrate failing rtstring ctor

Submitted by snrkiwi on Thu, 2010-10-21 20:12.

On Oct 18, 2010, at 11:23 , Peter Soetens wrote:

> On Tuesday 21 September 2010 13:19:15 Stephen Roderick wrote:
>> On Sep 21, 2010, at 03:26 , Peter Soetens wrote:
>>> On Tuesday 21 September 2010 02:55:22 S Roderick wrote:
>>>> Attached patches add a test to OCL v1 to create rtstring instances in
>>>> scripting. The test fails to use rtstring ctor, and instead attempts to
>>>> create a string (ie std::string) first and then create rstring from
>>>> that. This is bad.
>>>
>>> That's probably because std::string is hardcoded in the parsers, and it
>>> assumes every char* is going into a datasource of std::string. The only
>>> solution seems to be to pass it as a char* into a registered constructor
>>> for rt_string if a user writes it like this : rt_string("foo"), just
>>> like in C++.
>>
>> My test case has an example exactly like that, I believe. It fails.
>
> Could you add this as a bug report ? I'll loose track of it otherwise...
>
> Thanks,
>
> Peter

np

https://www.fmtc.be/bugzilla/orocos/show_bug.cgi?id=789

»

[PATCH] Demonstrate failing rtstring ctor

Submitted by snrkiwi on Thu, 2010-10-21 19:32.

On Oct 18, 2010, at 11:23 , Peter Soetens wrote:

> On Tuesday 21 September 2010 13:19:15 Stephen Roderick wrote:
>> On Sep 21, 2010, at 03:26 , Peter Soetens wrote:
>>> On Tuesday 21 September 2010 02:55:22 S Roderick wrote:
>>>> Attached patches add a test to OCL v1 to create rtstring instances in
>>>> scripting. The test fails to use rtstring ctor, and instead attempts to
>>>> create a string (ie std::string) first and then create rstring from
>>>> that. This is bad.
>>>
>>> That's probably because std::string is hardcoded in the parsers, and it
>>> assumes every char* is going into a datasource of std::string. The only
>>> solution seems to be to pass it as a char* into a registered constructor
>>> for rt_string if a user writes it like this : rt_string("foo"), just
>>> like in C++.
>>
>> My test case has an example exactly like that, I believe. It fails.
>
> Could you add this as a bug report ? I'll loose track of it otherwise...
>
> Thanks,
>
> Peter

np

https://www.fmtc.be/bugzilla/orocos/show_bug.cgi?id=789

»

[PATCH] Demonstrate failing rtstring ctor

Submitted by snrkiwi on Thu, 2010-10-21 18:52.

On Oct 18, 2010, at 11:23 , Peter Soetens wrote:

> On Tuesday 21 September 2010 13:19:15 Stephen Roderick wrote:
>> On Sep 21, 2010, at 03:26 , Peter Soetens wrote:
>>> On Tuesday 21 September 2010 02:55:22 S Roderick wrote:
>>>> Attached patches add a test to OCL v1 to create rtstring instances in
>>>> scripting. The test fails to use rtstring ctor, and instead attempts to
>>>> create a string (ie std::string) first and then create rstring from
>>>> that. This is bad.
>>>
>>> That's probably because std::string is hardcoded in the parsers, and it
>>> assumes every char* is going into a datasource of std::string. The only
>>> solution seems to be to pass it as a char* into a registered constructor
>>> for rt_string if a user writes it like this : rt_string("foo"), just
>>> like in C++.
>>
>> My test case has an example exactly like that, I believe. It fails.
>
> Could you add this as a bug report ? I'll loose track of it otherwise...
>
> Thanks,
>
> Peter

np

https://www.fmtc.be/bugzilla/orocos/show_bug.cgi?id=789

»

[PATCH] Demonstrate failing rtstring ctor

Submitted by snrkiwi on Thu, 2010-10-21 18:12.

On Oct 18, 2010, at 11:23 , Peter Soetens wrote:

> On Tuesday 21 September 2010 13:19:15 Stephen Roderick wrote:
>> On Sep 21, 2010, at 03:26 , Peter Soetens wrote:
>>> On Tuesday 21 September 2010 02:55:22 S Roderick wrote:
>>>> Attached patches add a test to OCL v1 to create rtstring instances in
>>>> scripting. The test fails to use rtstring ctor, and instead attempts to
>>>> create a string (ie std::string) first and then create rstring from
>>>> that. This is bad.
>>>
>>> That's probably because std::string is hardcoded in the parsers, and it
>>> assumes every char* is going into a datasource of std::string. The only
>>> solution seems to be to pass it as a char* into a registered constructor
>>> for rt_string if a user writes it like this : rt_string("foo"), just
>>> like in C++.
>>
>> My test case has an example exactly like that, I believe. It fails.
>
> Could you add this as a bug report ? I'll loose track of it otherwise...
>
> Thanks,
>
> Peter

np

https://www.fmtc.be/bugzilla/orocos/show_bug.cgi?id=789

»

[PATCH] Demonstrate failing rtstring ctor

Submitted by snrkiwi on Thu, 2010-10-21 17:36.

On Oct 18, 2010, at 11:23 , Peter Soetens wrote:

> On Tuesday 21 September 2010 13:19:15 Stephen Roderick wrote:
>> On Sep 21, 2010, at 03:26 , Peter Soetens wrote:
>>> On Tuesday 21 September 2010 02:55:22 S Roderick wrote:
>>>> Attached patches add a test to OCL v1 to create rtstring instances in
>>>> scripting. The test fails to use rtstring ctor, and instead attempts to
>>>> create a string (ie std::string) first and then create rstring from
>>>> that. This is bad.
>>>
>>> That's probably because std::string is hardcoded in the parsers, and it
>>> assumes every char* is going into a datasource of std::string. The only
>>> solution seems to be to pass it as a char* into a registered constructor
>>> for rt_string if a user writes it like this : rt_string("foo"), just
>>> like in C++.
>>
>> My test case has an example exactly like that, I believe. It fails.
>
> Could you add this as a bug report ? I'll loose track of it otherwise...
>
> Thanks,
>
> Peter

np

https://www.fmtc.be/bugzilla/orocos/show_bug.cgi?id=789

»

[PATCH] Demonstrate failing rtstring ctor

Submitted by snrkiwi on Thu, 2010-10-21 17:00.

On Oct 18, 2010, at 11:23 , Peter Soetens wrote:

> On Tuesday 21 September 2010 13:19:15 Stephen Roderick wrote:
>> On Sep 21, 2010, at 03:26 , Peter Soetens wrote:
>>> On Tuesday 21 September 2010 02:55:22 S Roderick wrote:
>>>> Attached patches add a test to OCL v1 to create rtstring instances in
>>>> scripting. The test fails to use rtstring ctor, and instead attempts to
>>>> create a string (ie std::string) first and then create rstring from
>>>> that. This is bad.
>>>
>>> That's probably because std::string is hardcoded in the parsers, and it
>>> assumes every char* is going into a datasource of std::string. The only
>>> solution seems to be to pass it as a char* into a registered constructor
>>> for rt_string if a user writes it like this : rt_string("foo"), just
>>> like in C++.
>>
>> My test case has an example exactly like that, I believe. It fails.
>
> Could you add this as a bug report ? I'll loose track of it otherwise...
>
> Thanks,
>
> Peter

np

https://www.fmtc.be/bugzilla/orocos/show_bug.cgi?id=789

»

[PATCH] Demonstrate failing rtstring ctor

Submitted by snrkiwi on Thu, 2010-10-21 16:24.

On Oct 18, 2010, at 11:23 , Peter Soetens wrote:

> On Tuesday 21 September 2010 13:19:15 Stephen Roderick wrote:
>> On Sep 21, 2010, at 03:26 , Peter Soetens wrote:
>>> On Tuesday 21 September 2010 02:55:22 S Roderick wrote:
>>>> Attached patches add a test to OCL v1 to create rtstring instances in
>>>> scripting. The test fails to use rtstring ctor, and instead attempts to
>>>> create a string (ie std::string) first and then create rstring from
>>>> that. This is bad.
>>>
>>> That's probably because std::string is hardcoded in the parsers, and it
>>> assumes every char* is going into a datasource of std::string. The only
>>> solution seems to be to pass it as a char* into a registered constructor
>>> for rt_string if a user writes it like this : rt_string("foo"), just
>>> like in C++.
>>
>> My test case has an example exactly like that, I believe. It fails.
>
> Could you add this as a bug report ? I'll loose track of it otherwise...
>
> Thanks,
>
> Peter

np

https://www.fmtc.be/bugzilla/orocos/show_bug.cgi?id=789

»

[PATCH] Demonstrate failing rtstring ctor

Submitted by snrkiwi on Thu, 2010-10-21 15:48.

On Oct 18, 2010, at 11:23 , Peter Soetens wrote:

> On Tuesday 21 September 2010 13:19:15 Stephen Roderick wrote:
>> On Sep 21, 2010, at 03:26 , Peter Soetens wrote:
>>> On Tuesday 21 September 2010 02:55:22 S Roderick wrote:
>>>> Attached patches add a test to OCL v1 to create rtstring instances in
>>>> scripting. The test fails to use rtstring ctor, and instead attempts to
>>>> create a string (ie std::string) first and then create rstring from
>>>> that. This is bad.
>>>
>>> That's probably because std::string is hardcoded in the parsers, and it
>>> assumes every char* is going into a datasource of std::string. The only
>>> solution seems to be to pass it as a char* into a registered constructor
>>> for rt_string if a user writes it like this : rt_string("foo"), just
>>> like in C++.
>>
>> My test case has an example exactly like that, I believe. It fails.
>
> Could you add this as a bug report ? I'll loose track of it otherwise...
>
> Thanks,
>
> Peter

np

https://www.fmtc.be/bugzilla/orocos/show_bug.cgi?id=789

»

[PATCH] Demonstrate failing rtstring ctor

Submitted by snrkiwi on Thu, 2010-10-21 15:12.

On Oct 18, 2010, at 11:23 , Peter Soetens wrote:

> On Tuesday 21 September 2010 13:19:15 Stephen Roderick wrote:
>> On Sep 21, 2010, at 03:26 , Peter Soetens wrote:
>>> On Tuesday 21 September 2010 02:55:22 S Roderick wrote:
>>>> Attached patches add a test to OCL v1 to create rtstring instances in
>>>> scripting. The test fails to use rtstring ctor, and instead attempts to
>>>> create a string (ie std::string) first and then create rstring from
>>>> that. This is bad.
>>>
>>> That's probably because std::string is hardcoded in the parsers, and it
>>> assumes every char* is going into a datasource of std::string. The only
>>> solution seems to be to pass it as a char* into a registered constructor
>>> for rt_string if a user writes it like this : rt_string("foo"), just
>>> like in C++.
>>
>> My test case has an example exactly like that, I believe. It fails.
>
> Could you add this as a bug report ? I'll loose track of it otherwise...
>
> Thanks,
>
> Peter

np

https://www.fmtc.be/bugzilla/orocos/show_bug.cgi?id=789

»

[PATCH] Demonstrate failing rtstring ctor

Submitted by snrkiwi on Thu, 2010-10-21 14:36.

On Oct 18, 2010, at 11:23 , Peter Soetens wrote:

> On Tuesday 21 September 2010 13:19:15 Stephen Roderick wrote:
>> On Sep 21, 2010, at 03:26 , Peter Soetens wrote:
>>> On Tuesday 21 September 2010 02:55:22 S Roderick wrote:
>>>> Attached patches add a test to OCL v1 to create rtstring instances in
>>>> scripting. The test fails to use rtstring ctor, and instead attempts to
>>>> create a string (ie std::string) first and then create rstring from
>>>> that. This is bad.
>>>
>>> That's probably because std::string is hardcoded in the parsers, and it
>>> assumes every char* is going into a datasource of std::string. The only
>>> solution seems to be to pass it as a char* into a registered constructor
>>> for rt_string if a user writes it like this : rt_string("foo"), just
>>> like in C++.
>>
>> My test case has an example exactly like that, I believe. It fails.
>
> Could you add this as a bug report ? I'll loose track of it otherwise...
>
> Thanks,
>
> Peter

np

https://www.fmtc.be/bugzilla/orocos/show_bug.cgi?id=789

»

[PATCH] Demonstrate failing rtstring ctor

Submitted by snrkiwi on Thu, 2010-10-21 14:00.

On Oct 18, 2010, at 11:23 , Peter Soetens wrote:

> On Tuesday 21 September 2010 13:19:15 Stephen Roderick wrote:
>> On Sep 21, 2010, at 03:26 , Peter Soetens wrote:
>>> On Tuesday 21 September 2010 02:55:22 S Roderick wrote:
>>>> Attached patches add a test to OCL v1 to create rtstring instances in
>>>> scripting. The test fails to use rtstring ctor, and instead attempts to
>>>> create a string (ie std::string) first and then create rstring from
>>>> that. This is bad.
>>>
>>> That's probably because std::string is hardcoded in the parsers, and it
>>> assumes every char* is going into a datasource of std::string. The only
>>> solution seems to be to pass it as a char* into a registered constructor
>>> for rt_string if a user writes it like this : rt_string("foo"), just
>>> like in C++.
>>
>> My test case has an example exactly like that, I believe. It fails.
>
> Could you add this as a bug report ? I'll loose track of it otherwise...
>
> Thanks,
>
> Peter

np

https://www.fmtc.be/bugzilla/orocos/show_bug.cgi?id=789

»

[PATCH] Demonstrate failing rtstring ctor

Submitted by snrkiwi on Thu, 2010-10-21 13:24.

On Oct 18, 2010, at 11:23 , Peter Soetens wrote:

> On Tuesday 21 September 2010 13:19:15 Stephen Roderick wrote:
>> On Sep 21, 2010, at 03:26 , Peter Soetens wrote:
>>> On Tuesday 21 September 2010 02:55:22 S Roderick wrote:
>>>> Attached patches add a test to OCL v1 to create rtstring instances in
>>>> scripting. The test fails to use rtstring ctor, and instead attempts to
>>>> create a string (ie std::string) first and then create rstring from
>>>> that. This is bad.
>>>
>>> That's probably because std::string is hardcoded in the parsers, and it
>>> assumes every char* is going into a datasource of std::string. The only
>>> solution seems to be to pass it as a char* into a registered constructor
>>> for rt_string if a user writes it like this : rt_string("foo"), just
>>> like in C++.
>>
>> My test case has an example exactly like that, I believe. It fails.
>
> Could you add this as a bug report ? I'll loose track of it otherwise...
>
> Thanks,
>
> Peter

np

https://www.fmtc.be/bugzilla/orocos/show_bug.cgi?id=789

»

[PATCH] Demonstrate failing rtstring ctor

Submitted by snrkiwi on Thu, 2010-10-21 12:44.

On Oct 18, 2010, at 11:23 , Peter Soetens wrote:

> On Tuesday 21 September 2010 13:19:15 Stephen Roderick wrote:
>> On Sep 21, 2010, at 03:26 , Peter Soetens wrote:
>>> On Tuesday 21 September 2010 02:55:22 S Roderick wrote:
>>>> Attached patches add a test to OCL v1 to create rtstring instances in
>>>> scripting. The test fails to use rtstring ctor, and instead attempts to
>>>> create a string (ie std::string) first and then create rstring from
>>>> that. This is bad.
>>>
>>> That's probably because std::string is hardcoded in the parsers, and it
>>> assumes every char* is going into a datasource of std::string. The only
>>> solution seems to be to pass it as a char* into a registered constructor
>>> for rt_string if a user writes it like this : rt_string("foo"), just
>>> like in C++.
>>
>> My test case has an example exactly like that, I believe. It fails.
>
> Could you add this as a bug report ? I'll loose track of it otherwise...
>
> Thanks,
>
> Peter

np

https://www.fmtc.be/bugzilla/orocos/show_bug.cgi?id=789

»

[PATCH] Demonstrate failing rtstring ctor

Submitted by snrkiwi on Thu, 2010-10-21 12:08.

On Oct 18, 2010, at 11:23 , Peter Soetens wrote:

> On Tuesday 21 September 2010 13:19:15 Stephen Roderick wrote:
>> On Sep 21, 2010, at 03:26 , Peter Soetens wrote:
>>> On Tuesday 21 September 2010 02:55:22 S Roderick wrote:
>>>> Attached patches add a test to OCL v1 to create rtstring instances in
>>>> scripting. The test fails to use rtstring ctor, and instead attempts to
>>>> create a string (ie std::string) first and then create rstring from
>>>> that. This is bad.
>>>
>>> That's probably because std::string is hardcoded in the parsers, and it
>>> assumes every char* is going into a datasource of std::string. The only
>>> solution seems to be to pass it as a char* into a registered constructor
>>> for rt_string if a user writes it like this : rt_string("foo"), just
>>> like in C++.
>>
>> My test case has an example exactly like that, I believe. It fails.
>
> Could you add this as a bug report ? I'll loose track of it otherwise...
>
> Thanks,
>
> Peter

np

https://www.fmtc.be/bugzilla/orocos/show_bug.cgi?id=789

»

[PATCH] Demonstrate failing rtstring ctor

Submitted by snrkiwi on Thu, 2010-10-21 11:36.

On Oct 18, 2010, at 11:23 , Peter Soetens wrote:

> On Tuesday 21 September 2010 13:19:15 Stephen Roderick wrote:
>> On Sep 21, 2010, at 03:26 , Peter Soetens wrote:
>>> On Tuesday 21 September 2010 02:55:22 S Roderick wrote:
>>>> Attached patches add a test to OCL v1 to create rtstring instances in
>>>> scripting. The test fails to use rtstring ctor, and instead attempts to
>>>> create a string (ie std::string) first and then create rstring from
>>>> that. This is bad.
>>>
>>> That's probably because std::string is hardcoded in the parsers, and it
>>> assumes every char* is going into a datasource of std::string. The only
>>> solution seems to be to pass it as a char* into a registered constructor
>>> for rt_string if a user writes it like this : rt_string("foo"), just
>>> like in C++.
>>
>> My test case has an example exactly like that, I believe. It fails.
>
> Could you add this as a bug report ? I'll loose track of it otherwise...
>
> Thanks,
>
> Peter

np

https://www.fmtc.be/bugzilla/orocos/show_bug.cgi?id=789

»

[PATCH] Demonstrate failing rtstring ctor

Submitted by snrkiwi on Thu, 2010-10-21 11:04.

On Oct 18, 2010, at 11:23 , Peter Soetens wrote:

> On Tuesday 21 September 2010 13:19:15 Stephen Roderick wrote:
>> On Sep 21, 2010, at 03:26 , Peter Soetens wrote:
>>> On Tuesday 21 September 2010 02:55:22 S Roderick wrote:
>>>> Attached patches add a test to OCL v1 to create rtstring instances in
>>>> scripting. The test fails to use rtstring ctor, and instead attempts to
>>>> create a string (ie std::string) first and then create rstring from
>>>> that. This is bad.
>>>
>>> That's probably because std::string is hardcoded in the parsers, and it
>>> assumes every char* is going into a datasource of std::string. The only
>>> solution seems to be to pass it as a char* into a registered constructor
>>> for rt_string if a user writes it like this : rt_string("foo"), just
>>> like in C++.
>>
>> My test case has an example exactly like that, I believe. It fails.
>
> Could you add this as a bug report ? I'll loose track of it otherwise...
>
> Thanks,
>
> Peter

np

https://www.fmtc.be/bugzilla/orocos/show_bug.cgi?id=789

»

[PATCH] Demonstrate failing rtstring ctor

Submitted by snrkiwi on Thu, 2010-10-21 10:32.

On Oct 18, 2010, at 11:23 , Peter Soetens wrote:

> On Tuesday 21 September 2010 13:19:15 Stephen Roderick wrote:
>> On Sep 21, 2010, at 03:26 , Peter Soetens wrote:
>>> On Tuesday 21 September 2010 02:55:22 S Roderick wrote:
>>>> Attached patches add a test to OCL v1 to create rtstring instances in
>>>> scripting. The test fails to use rtstring ctor, and instead attempts to
>>>> create a string (ie std::string) first and then create rstring from
>>>> that. This is bad.
>>>
>>> That's probably because std::string is hardcoded in the parsers, and it
>>> assumes every char* is going into a datasource of std::string. The only
>>> solution seems to be to pass it as a char* into a registered constructor
>>> for rt_string if a user writes it like this : rt_string("foo"), just
>>> like in C++.
>>
>> My test case has an example exactly like that, I believe. It fails.
>
> Could you add this as a bug report ? I'll loose track of it otherwise...
>
> Thanks,
>
> Peter

np

https://www.fmtc.be/bugzilla/orocos/show_bug.cgi?id=789

»

[PATCH] Demonstrate failing rtstring ctor

Submitted by snrkiwi on Thu, 2010-10-21 10:00.

On Oct 18, 2010, at 11:23 , Peter Soetens wrote:

> On Tuesday 21 September 2010 13:19:15 Stephen Roderick wrote:
>> On Sep 21, 2010, at 03:26 , Peter Soetens wrote:
>>> On Tuesday 21 September 2010 02:55:22 S Roderick wrote:
>>>> Attached patches add a test to OCL v1 to create rtstring instances in
>>>> scripting. The test fails to use rtstring ctor, and instead attempts to
>>>> create a string (ie std::string) first and then create rstring from
>>>> that. This is bad.
>>>
>>> That's probably because std::string is hardcoded in the parsers, and it
>>> assumes every char* is going into a datasource of std::string. The only
>>> solution seems to be to pass it as a char* into a registered constructor
>>> for rt_string if a user writes it like this : rt_string("foo"), just
>>> like in C++.
>>
>> My test case has an example exactly like that, I believe. It fails.
>
> Could you add this as a bug report ? I'll loose track of it otherwise...
>
> Thanks,
>
> Peter

np

https://www.fmtc.be/bugzilla/orocos/show_bug.cgi?id=789

»

[PATCH] Demonstrate failing rtstring ctor

Submitted by snrkiwi on Thu, 2010-10-21 09:28.

On Oct 18, 2010, at 11:23 , Peter Soetens wrote:

> On Tuesday 21 September 2010 13:19:15 Stephen Roderick wrote:
>> On Sep 21, 2010, at 03:26 , Peter Soetens wrote:
>>> On Tuesday 21 September 2010 02:55:22 S Roderick wrote:
>>>> Attached patches add a test to OCL v1 to create rtstring instances in
>>>> scripting. The test fails to use rtstring ctor, and instead attempts to
>>>> create a string (ie std::string) first and then create rstring from
>>>> that. This is bad.
>>>
>>> That's probably because std::string is hardcoded in the parsers, and it
>>> assumes every char* is going into a datasource of std::string. The only
>>> solution seems to be to pass it as a char* into a registered constructor
>>> for rt_string if a user writes it like this : rt_string("foo"), just
>>> like in C++.
>>
>> My test case has an example exactly like that, I believe. It fails.
>
> Could you add this as a bug report ? I'll loose track of it otherwise...
>
> Thanks,
>
> Peter

np

https://www.fmtc.be/bugzilla/orocos/show_bug.cgi?id=789

»

[PATCH] Demonstrate failing rtstring ctor

Submitted by snrkiwi on Thu, 2010-10-21 08:56.

On Oct 18, 2010, at 11:23 , Peter Soetens wrote:

> On Tuesday 21 September 2010 13:19:15 Stephen Roderick wrote:
>> On Sep 21, 2010, at 03:26 , Peter Soetens wrote:
>>> On Tuesday 21 September 2010 02:55:22 S Roderick wrote:
>>>> Attached patches add a test to OCL v1 to create rtstring instances in
>>>> scripting. The test fails to use rtstring ctor, and instead attempts to
>>>> create a string (ie std::string) first and then create rstring from
>>>> that. This is bad.
>>>
>>> That's probably because std::string is hardcoded in the parsers, and it
>>> assumes every char* is going into a datasource of std::string. The only
>>> solution seems to be to pass it as a char* into a registered constructor
>>> for rt_string if a user writes it like this : rt_string("foo"), just
>>> like in C++.
>>
>> My test case has an example exactly like that, I believe. It fails.
>
> Could you add this as a bug report ? I'll loose track of it otherwise...
>
> Thanks,
>
> Peter

np

https://www.fmtc.be/bugzilla/orocos/show_bug.cgi?id=789

»

[PATCH] Demonstrate failing rtstring ctor

Submitted by snrkiwi on Thu, 2010-10-21 08:24.

On Oct 18, 2010, at 11:23 , Peter Soetens wrote:

> On Tuesday 21 September 2010 13:19:15 Stephen Roderick wrote:
>> On Sep 21, 2010, at 03:26 , Peter Soetens wrote:
>>> On Tuesday 21 September 2010 02:55:22 S Roderick wrote:
>>>> Attached patches add a test to OCL v1 to create rtstring instances in
>>>> scripting. The test fails to use rtstring ctor, and instead attempts to
>>>> create a string (ie std::string) first and then create rstring from
>>>> that. This is bad.
>>>
>>> That's probably because std::string is hardcoded in the parsers, and it
>>> assumes every char* is going into a datasource of std::string. The only
>>> solution seems to be to pass it as a char* into a registered constructor
>>> for rt_string if a user writes it like this : rt_string("foo"), just
>>> like in C++.
>>
>> My test case has an example exactly like that, I believe. It fails.
>
> Could you add this as a bug report ? I'll loose track of it otherwise...
>
> Thanks,
>
> Peter

np

https://www.fmtc.be/bugzilla/orocos/show_bug.cgi?id=789

»

[PATCH] Demonstrate failing rtstring ctor

Submitted by snrkiwi on Thu, 2010-10-21 07:52.

On Oct 18, 2010, at 11:23 , Peter Soetens wrote:

> On Tuesday 21 September 2010 13:19:15 Stephen Roderick wrote:
>> On Sep 21, 2010, at 03:26 , Peter Soetens wrote:
>>> On Tuesday 21 September 2010 02:55:22 S Roderick wrote:
>>>> Attached patches add a test to OCL v1 to create rtstring instances in
>>>> scripting. The test fails to use rtstring ctor, and instead attempts to
>>>> create a string (ie std::string) first and then create rstring from
>>>> that. This is bad.
>>>
>>> That's probably because std::string is hardcoded in the parsers, and it
>>> assumes every char* is going into a datasource of std::string. The only
>>> solution seems to be to pass it as a char* into a registered constructor
>>> for rt_string if a user writes it like this : rt_string("foo"), just
>>> like in C++.
>>
>> My test case has an example exactly like that, I believe. It fails.
>
> Could you add this as a bug report ? I'll loose track of it otherwise...
>
> Thanks,
>
> Peter

np

https://www.fmtc.be/bugzilla/orocos/show_bug.cgi?id=789

»

[PATCH] Demonstrate failing rtstring ctor

Submitted by snrkiwi on Thu, 2010-10-21 07:20.

On Oct 18, 2010, at 11:23 , Peter Soetens wrote:

> On Tuesday 21 September 2010 13:19:15 Stephen Roderick wrote:
>> On Sep 21, 2010, at 03:26 , Peter Soetens wrote:
>>> On Tuesday 21 September 2010 02:55:22 S Roderick wrote:
>>>> Attached patches add a test to OCL v1 to create rtstring instances in
>>>> scripting. The test fails to use rtstring ctor, and instead attempts to
>>>> create a string (ie std::string) first and then create rstring from
>>>> that. This is bad.
>>>
>>> That's probably because std::string is hardcoded in the parsers, and it
>>> assumes every char* is going into a datasource of std::string. The only
>>> solution seems to be to pass it as a char* into a registered constructor
>>> for rt_string if a user writes it like this : rt_string("foo"), just
>>> like in C++.
>>
>> My test case has an example exactly like that, I believe. It fails.
>
> Could you add this as a bug report ? I'll loose track of it otherwise...
>
> Thanks,
>
> Peter

np

https://www.fmtc.be/bugzilla/orocos/show_bug.cgi?id=789

»

[PATCH] Demonstrate failing rtstring ctor

Submitted by snrkiwi on Thu, 2010-10-21 06:48.

On Oct 18, 2010, at 11:23 , Peter Soetens wrote:

> On Tuesday 21 September 2010 13:19:15 Stephen Roderick wrote:
>> On Sep 21, 2010, at 03:26 , Peter Soetens wrote:
>>> On Tuesday 21 September 2010 02:55:22 S Roderick wrote:
>>>> Attached patches add a test to OCL v1 to create rtstring instances in
>>>> scripting. The test fails to use rtstring ctor, and instead attempts to
>>>> create a string (ie std::string) first and then create rstring from
>>>> that. This is bad.
>>>
>>> That's probably because std::string is hardcoded in the parsers, and it
>>> assumes every char* is going into a datasource of std::string. The only
>>> solution seems to be to pass it as a char* into a registered constructor
>>> for rt_string if a user writes it like this : rt_string("foo"), just
>>> like in C++.
>>
>> My test case has an example exactly like that, I believe. It fails.
>
> Could you add this as a bug report ? I'll loose track of it otherwise...
>
> Thanks,
>
> Peter

np

https://www.fmtc.be/bugzilla/orocos/show_bug.cgi?id=789

»

[PATCH] Demonstrate failing rtstring ctor

Submitted by snrkiwi on Thu, 2010-10-21 06:16.

On Oct 18, 2010, at 11:23 , Peter Soetens wrote:

> On Tuesday 21 September 2010 13:19:15 Stephen Roderick wrote:
>> On Sep 21, 2010, at 03:26 , Peter Soetens wrote:
>>> On Tuesday 21 September 2010 02:55:22 S Roderick wrote:
>>>> Attached patches add a test to OCL v1 to create rtstring instances in
>>>> scripting. The test fails to use rtstring ctor, and instead attempts to
>>>> create a string (ie std::string) first and then create rstring from
>>>> that. This is bad.
>>>
>>> That's probably because std::string is hardcoded in the parsers, and it
>>> assumes every char* is going into a datasource of std::string. The only
>>> solution seems to be to pass it as a char* into a registered constructor
>>> for rt_string if a user writes it like this : rt_string("foo"), just
>>> like in C++.
>>
>> My test case has an example exactly like that, I believe. It fails.
>
> Could you add this as a bug report ? I'll loose track of it otherwise...
>
> Thanks,
>
> Peter

np

https://www.fmtc.be/bugzilla/orocos/show_bug.cgi?id=789

»

[PATCH] Demonstrate failing rtstring ctor

Submitted by snrkiwi on Thu, 2010-10-21 05:44.

On Oct 18, 2010, at 11:23 , Peter Soetens wrote:

> On Tuesday 21 September 2010 13:19:15 Stephen Roderick wrote:
>> On Sep 21, 2010, at 03:26 , Peter Soetens wrote:
>>> On Tuesday 21 September 2010 02:55:22 S Roderick wrote:
>>>> Attached patches add a test to OCL v1 to create rtstring instances in
>>>> scripting. The test fails to use rtstring ctor, and instead attempts to
>>>> create a string (ie std::string) first and then create rstring from
>>>> that. This is bad.
>>>
>>> That's probably because std::string is hardcoded in the parsers, and it
>>> assumes every char* is going into a datasource of std::string. The only
>>> solution seems to be to pass it as a char* into a registered constructor
>>> for rt_string if a user writes it like this : rt_string("foo"), just
>>> like in C++.
>>
>> My test case has an example exactly like that, I believe. It fails.
>
> Could you add this as a bug report ? I'll loose track of it otherwise...
>
> Thanks,
>
> Peter

np

https://www.fmtc.be/bugzilla/orocos/show_bug.cgi?id=789

»

[PATCH] Demonstrate failing rtstring ctor

Submitted by snrkiwi on Thu, 2010-10-21 05:12.

On Oct 18, 2010, at 11:23 , Peter Soetens wrote:

> On Tuesday 21 September 2010 13:19:15 Stephen Roderick wrote:
>> On Sep 21, 2010, at 03:26 , Peter Soetens wrote:
>>> On Tuesday 21 September 2010 02:55:22 S Roderick wrote:
>>>> Attached patches add a test to OCL v1 to create rtstring instances in
>>>> scripting. The test fails to use rtstring ctor, and instead attempts to
>>>> create a string (ie std::string) first and then create rstring from
>>>> that. This is bad.
>>>
>>> That's probably because std::string is hardcoded in the parsers, and it
>>> assumes every char* is going into a datasource of std::string. The only
>>> solution seems to be to pass it as a char* into a registered constructor
>>> for rt_string if a user writes it like this : rt_string("foo"), just
>>> like in C++.
>>
>> My test case has an example exactly like that, I believe. It fails.
>
> Could you add this as a bug report ? I'll loose track of it otherwise...
>
> Thanks,
>
> Peter

np

https://www.fmtc.be/bugzilla/orocos/show_bug.cgi?id=789

»

[PATCH] Demonstrate failing rtstring ctor

Submitted by snrkiwi on Thu, 2010-10-21 04:40.

On Oct 18, 2010, at 11:23 , Peter Soetens wrote:

> On Tuesday 21 September 2010 13:19:15 Stephen Roderick wrote:
>> On Sep 21, 2010, at 03:26 , Peter Soetens wrote:
>>> On Tuesday 21 September 2010 02:55:22 S Roderick wrote:
>>>> Attached patches add a test to OCL v1 to create rtstring instances in
>>>> scripting. The test fails to use rtstring ctor, and instead attempts to
>>>> create a string (ie std::string) first and then create rstring from
>>>> that. This is bad.
>>>
>>> That's probably because std::string is hardcoded in the parsers, and it
>>> assumes every char* is going into a datasource of std::string. The only
>>> solution seems to be to pass it as a char* into a registered constructor
>>> for rt_string if a user writes it like this : rt_string("foo"), just
>>> like in C++.
>>
>> My test case has an example exactly like that, I believe. It fails.
>
> Could you add this as a bug report ? I'll loose track of it otherwise...
>
> Thanks,
>
> Peter

np

https://www.fmtc.be/bugzilla/orocos/show_bug.cgi?id=789

»

[PATCH] Demonstrate failing rtstring ctor

Submitted by snrkiwi on Thu, 2010-10-21 04:08.

On Oct 18, 2010, at 11:23 , Peter Soetens wrote:

> On Tuesday 21 September 2010 13:19:15 Stephen Roderick wrote:
>> On Sep 21, 2010, at 03:26 , Peter Soetens wrote:
>>> On Tuesday 21 September 2010 02:55:22 S Roderick wrote:
>>>> Attached patches add a test to OCL v1 to create rtstring instances in
>>>> scripting. The test fails to use rtstring ctor, and instead attempts to
>>>> create a string (ie std::string) first and then create rstring from
>>>> that. This is bad.
>>>
>>> That's probably because std::string is hardcoded in the parsers, and it
>>> assumes every char* is going into a datasource of std::string. The only
>>> solution seems to be to pass it as a char* into a registered constructor
>>> for rt_string if a user writes it like this : rt_string("foo"), just
>>> like in C++.
>>
>> My test case has an example exactly like that, I believe. It fails.
>
> Could you add this as a bug report ? I'll loose track of it otherwise...
>
> Thanks,
>
> Peter

np

https://www.fmtc.be/bugzilla/orocos/show_bug.cgi?id=789

»

[PATCH] Demonstrate failing rtstring ctor

Submitted by snrkiwi on Thu, 2010-10-21 03:36.

On Oct 18, 2010, at 11:23 , Peter Soetens wrote:

> On Tuesday 21 September 2010 13:19:15 Stephen Roderick wrote:
>> On Sep 21, 2010, at 03:26 , Peter Soetens wrote:
>>> On Tuesday 21 September 2010 02:55:22 S Roderick wrote:
>>>> Attached patches add a test to OCL v1 to create rtstring instances in
>>>> scripting. The test fails to use rtstring ctor, and instead attempts to
>>>> create a string (ie std::string) first and then create rstring from
>>>> that. This is bad.
>>>
>>> That's probably because std::string is hardcoded in the parsers, and it
>>> assumes every char* is going into a datasource of std::string. The only
>>> solution seems to be to pass it as a char* into a registered constructor
>>> for rt_string if a user writes it like this : rt_string("foo"), just
>>> like in C++.
>>
>> My test case has an example exactly like that, I believe. It fails.
>
> Could you add this as a bug report ? I'll loose track of it otherwise...
>
> Thanks,
>
> Peter

np

https://www.fmtc.be/bugzilla/orocos/show_bug.cgi?id=789

»

[PATCH] Demonstrate failing rtstring ctor

Submitted by snrkiwi on Thu, 2010-10-21 03:04.

On Oct 18, 2010, at 11:23 , Peter Soetens wrote:

> On Tuesday 21 September 2010 13:19:15 Stephen Roderick wrote:
>> On Sep 21, 2010, at 03:26 , Peter Soetens wrote:
>>> On Tuesday 21 September 2010 02:55:22 S Roderick wrote:
>>>> Attached patches add a test to OCL v1 to create rtstring instances in
>>>> scripting. The test fails to use rtstring ctor, and instead attempts to
>>>> create a string (ie std::string) first and then create rstring from
>>>> that. This is bad.
>>>
>>> That's probably because std::string is hardcoded in the parsers, and it
>>> assumes every char* is going into a datasource of std::string. The only
>>> solution seems to be to pass it as a char* into a registered constructor
>>> for rt_string if a user writes it like this : rt_string("foo"), just
>>> like in C++.
>>
>> My test case has an example exactly like that, I believe. It fails.
>
> Could you add this as a bug report ? I'll loose track of it otherwise...
>
> Thanks,
>
> Peter

np

https://www.fmtc.be/bugzilla/orocos/show_bug.cgi?id=789

»

[PATCH] Demonstrate failing rtstring ctor

Submitted by snrkiwi on Thu, 2010-10-21 02:32.

On Oct 18, 2010, at 11:23 , Peter Soetens wrote:

> On Tuesday 21 September 2010 13:19:15 Stephen Roderick wrote:
>> On Sep 21, 2010, at 03:26 , Peter Soetens wrote:
>>> On Tuesday 21 September 2010 02:55:22 S Roderick wrote:
>>>> Attached patches add a test to OCL v1 to create rtstring instances in
>>>> scripting. The test fails to use rtstring ctor, and instead attempts to
>>>> create a string (ie std::string) first and then create rstring from
>>>> that. This is bad.
>>>
>>> That's probably because std::string is hardcoded in the parsers, and it
>>> assumes every char* is going into a datasource of std::string. The only
>>> solution seems to be to pass it as a char* into a registered constructor
>>> for rt_string if a user writes it like this : rt_string("foo"), just
>>> like in C++.
>>
>> My test case has an example exactly like that, I believe. It fails.
>
> Could you add this as a bug report ? I'll loose track of it otherwise...
>
> Thanks,
>
> Peter

np

https://www.fmtc.be/bugzilla/orocos/show_bug.cgi?id=789

»

[PATCH] Demonstrate failing rtstring ctor

Submitted by snrkiwi on Thu, 2010-10-21 02:00.

On Oct 18, 2010, at 11:23 , Peter Soetens wrote:

> On Tuesday 21 September 2010 13:19:15 Stephen Roderick wrote:
>> On Sep 21, 2010, at 03:26 , Peter Soetens wrote:
>>> On Tuesday 21 September 2010 02:55:22 S Roderick wrote:
>>>> Attached patches add a test to OCL v1 to create rtstring instances in
>>>> scripting. The test fails to use rtstring ctor, and instead attempts to
>>>> create a string (ie std::string) first and then create rstring from
>>>> that. This is bad.
>>>
>>> That's probably because std::string is hardcoded in the parsers, and it
>>> assumes every char* is going into a datasource of std::string. The only
>>> solution seems to be to pass it as a char* into a registered constructor
>>> for rt_string if a user writes it like this : rt_string("foo"), just
>>> like in C++.
>>
>> My test case has an example exactly like that, I believe. It fails.
>
> Could you add this as a bug report ? I'll loose track of it otherwise...
>
> Thanks,
>
> Peter

np

https://www.fmtc.be/bugzilla/orocos/show_bug.cgi?id=789

»

[PATCH] Demonstrate failing rtstring ctor

Submitted by snrkiwi on Thu, 2010-10-21 01:28.

On Oct 18, 2010, at 11:23 , Peter Soetens wrote:

> On Tuesday 21 September 2010 13:19:15 Stephen Roderick wrote:
>> On Sep 21, 2010, at 03:26 , Peter Soetens wrote:
>>> On Tuesday 21 September 2010 02:55:22 S Roderick wrote:
>>>> Attached patches add a test to OCL v1 to create rtstring instances in
>>>> scripting. The test fails to use rtstring ctor, and instead attempts to
>>>> create a string (ie std::string) first and then create rstring from
>>>> that. This is bad.
>>>
>>> That's probably because std::string is hardcoded in the parsers, and it
>>> assumes every char* is going into a datasource of std::string. The only
>>> solution seems to be to pass it as a char* into a registered constructor
>>> for rt_string if a user writes it like this : rt_string("foo"), just
>>> like in C++.
>>
>> My test case has an example exactly like that, I believe. It fails.
>
> Could you add this as a bug report ? I'll loose track of it otherwise...
>
> Thanks,
>
> Peter

np

https://www.fmtc.be/bugzilla/orocos/show_bug.cgi?id=789

»

[PATCH] Demonstrate failing rtstring ctor

Submitted by snrkiwi on Thu, 2010-10-21 00:56.

On Oct 18, 2010, at 11:23 , Peter Soetens wrote:

> On Tuesday 21 September 2010 13:19:15 Stephen Roderick wrote:
>> On Sep 21, 2010, at 03:26 , Peter Soetens wrote:
>>> On Tuesday 21 September 2010 02:55:22 S Roderick wrote:
>>>> Attached patches add a test to OCL v1 to create rtstring instances in
>>>> scripting. The test fails to use rtstring ctor, and instead attempts to
>>>> create a string (ie std::string) first and then create rstring from
>>>> that. This is bad.
>>>
>>> That's probably because std::string is hardcoded in the parsers, and it
>>> assumes every char* is going into a datasource of std::string. The only
>>> solution seems to be to pass it as a char* into a registered constructor
>>> for rt_string if a user writes it like this : rt_string("foo"), just
>>> like in C++.
>>
>> My test case has an example exactly like that, I believe. It fails.
>
> Could you add this as a bug report ? I'll loose track of it otherwise...
>
> Thanks,
>
> Peter

np

https://www.fmtc.be/bugzilla/orocos/show_bug.cgi?id=789

»

[PATCH] Demonstrate failing rtstring ctor

Submitted by snrkiwi on Thu, 2010-10-21 00:24.

On Oct 18, 2010, at 11:23 , Peter Soetens wrote:

> On Tuesday 21 September 2010 13:19:15 Stephen Roderick wrote:
>> On Sep 21, 2010, at 03:26 , Peter Soetens wrote:
>>> On Tuesday 21 September 2010 02:55:22 S Roderick wrote:
>>>> Attached patches add a test to OCL v1 to create rtstring instances in
>>>> scripting. The test fails to use rtstring ctor, and instead attempts to
>>>> create a string (ie std::string) first and then create rstring from
>>>> that. This is bad.
>>>
>>> That's probably because std::string is hardcoded in the parsers, and it
>>> assumes every char* is going into a datasource of std::string. The only
>>> solution seems to be to pass it as a char* into a registered constructor
>>> for rt_string if a user writes it like this : rt_string("foo"), just
>>> like in C++.
>>
>> My test case has an example exactly like that, I believe. It fails.
>
> Could you add this as a bug report ? I'll loose track of it otherwise...
>
> Thanks,
>
> Peter

np

https://www.fmtc.be/bugzilla/orocos/show_bug.cgi?id=789

»

[PATCH] Demonstrate failing rtstring ctor

Submitted by snrkiwi on Wed, 2010-10-20 23:52.

On Oct 18, 2010, at 11:23 , Peter Soetens wrote:

> On Tuesday 21 September 2010 13:19:15 Stephen Roderick wrote:
>> On Sep 21, 2010, at 03:26 , Peter Soetens wrote:
>>> On Tuesday 21 September 2010 02:55:22 S Roderick wrote:
>>>> Attached patches add a test to OCL v1 to create rtstring instances in
>>>> scripting. The test fails to use rtstring ctor, and instead attempts to
>>>> create a string (ie std::string) first and then create rstring from
>>>> that. This is bad.
>>>
>>> That's probably because std::string is hardcoded in the parsers, and it
>>> assumes every char* is going into a datasource of std::string. The only
>>> solution seems to be to pass it as a char* into a registered constructor
>>> for rt_string if a user writes it like this : rt_string("foo"), just
>>> like in C++.
>>
>> My test case has an example exactly like that, I believe. It fails.
>
> Could you add this as a bug report ? I'll loose track of it otherwise...
>
> Thanks,
>
> Peter

np

https://www.fmtc.be/bugzilla/orocos/show_bug.cgi?id=789

»

[PATCH] Demonstrate failing rtstring ctor

Submitted by snrkiwi on Wed, 2010-10-20 23:20.

On Oct 18, 2010, at 11:23 , Peter Soetens wrote:

> On Tuesday 21 September 2010 13:19:15 Stephen Roderick wrote:
>> On Sep 21, 2010, at 03:26 , Peter Soetens wrote:
>>> On Tuesday 21 September 2010 02:55:22 S Roderick wrote:
>>>> Attached patches add a test to OCL v1 to create rtstring instances in
>>>> scripting. The test fails to use rtstring ctor, and instead attempts to
>>>> create a string (ie std::string) first and then create rstring from
>>>> that. This is bad.
>>>
>>> That's probably because std::string is hardcoded in the parsers, and it
>>> assumes every char* is going into a datasource of std::string. The only
>>> solution seems to be to pass it as a char* into a registered constructor
>>> for rt_string if a user writes it like this : rt_string("foo"), just
>>> like in C++.
>>
>> My test case has an example exactly like that, I believe. It fails.
>
> Could you add this as a bug report ? I'll loose track of it otherwise...
>
> Thanks,
>
> Peter

np

https://www.fmtc.be/bugzilla/orocos/show_bug.cgi?id=789

»

[PATCH] Demonstrate failing rtstring ctor

Submitted by snrkiwi on Wed, 2010-10-20 22:48.

On Oct 18, 2010, at 11:23 , Peter Soetens wrote:

> On Tuesday 21 September 2010 13:19:15 Stephen Roderick wrote:
>> On Sep 21, 2010, at 03:26 , Peter Soetens wrote:
>>> On Tuesday 21 September 2010 02:55:22 S Roderick wrote:
>>>> Attached patches add a test to OCL v1 to create rtstring instances in
>>>> scripting. The test fails to use rtstring ctor, and instead attempts to
>>>> create a string (ie std::string) first and then create rstring from
>>>> that. This is bad.
>>>
>>> That's probably because std::string is hardcoded in the parsers, and it
>>> assumes every char* is going into a datasource of std::string. The only
>>> solution seems to be to pass it as a char* into a registered constructor
>>> for rt_string if a user writes it like this : rt_string("foo"), just
>>> like in C++.
>>
>> My test case has an example exactly like that, I believe. It fails.
>
> Could you add this as a bug report ? I'll loose track of it otherwise...
>
> Thanks,
>
> Peter

np

https://www.fmtc.be/bugzilla/orocos/show_bug.cgi?id=789

»