[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 Sat, 2010-10-23 19: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 Sat, 2010-10-23 19: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 Sat, 2010-10-23 18: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 Sat, 2010-10-23 17: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 Sat, 2010-10-23 16: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 Sat, 2010-10-23 15: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 Sat, 2010-10-23 14: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 Sat, 2010-10-23 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 Sat, 2010-10-23 12: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 Sat, 2010-10-23 11: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 Sat, 2010-10-23 10: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 Sat, 2010-10-23 09: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 Sat, 2010-10-23 08: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 Sat, 2010-10-23 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 Sat, 2010-10-23 06: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 Sat, 2010-10-23 06: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 Sat, 2010-10-23 05: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 Sat, 2010-10-23 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 Sat, 2010-10-23 03: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 Sat, 2010-10-23 02: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 Sat, 2010-10-23 01: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 Sat, 2010-10-23 00: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 Fri, 2010-10-22 23: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 Fri, 2010-10-22 23: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 Fri, 2010-10-22 22: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 Fri, 2010-10-22 21: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 Fri, 2010-10-22 20: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 Fri, 2010-10-22 19: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 19: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 Fri, 2010-10-22 18: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 Fri, 2010-10-22 17: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 Fri, 2010-10-22 16: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 Fri, 2010-10-22 16: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 Fri, 2010-10-22 15: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 Fri, 2010-10-22 14: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 13: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 Fri, 2010-10-22 13: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 Fri, 2010-10-22 12: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 Fri, 2010-10-22 11: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 Fri, 2010-10-22 11: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 Fri, 2010-10-22 10: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 Fri, 2010-10-22 09: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 Fri, 2010-10-22 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 Fri, 2010-10-22 08: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 07: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 06: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 06: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 05: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 04: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 04: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

»