[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 peter on Thu, 2010-10-21 07:20.

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

»

[PATCH] Demonstrate failing rtstring ctor

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

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

»

[PATCH] Demonstrate failing rtstring ctor

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

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

»

[PATCH] Demonstrate failing rtstring ctor

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

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

»

[PATCH] Demonstrate failing rtstring ctor

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

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

»

[PATCH] Demonstrate failing rtstring ctor

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

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

»

[PATCH] Demonstrate failing rtstring ctor

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

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

»

[PATCH] Demonstrate failing rtstring ctor

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

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

»

[PATCH] Demonstrate failing rtstring ctor

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

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

»

[PATCH] Demonstrate failing rtstring ctor

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

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

»

[PATCH] Demonstrate failing rtstring ctor

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

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

»

[PATCH] Demonstrate failing rtstring ctor

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

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

»

[PATCH] Demonstrate failing rtstring ctor

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

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

»

[PATCH] Demonstrate failing rtstring ctor

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

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

»

[PATCH] Demonstrate failing rtstring ctor

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

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

»

[PATCH] Demonstrate failing rtstring ctor

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

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

»

[PATCH] Demonstrate failing rtstring ctor

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

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

»

[PATCH] Demonstrate failing rtstring ctor

Submitted by peter on Wed, 2010-10-20 22:16.

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

»

[PATCH] Demonstrate failing rtstring ctor

Submitted by peter on Wed, 2010-10-20 21:44.

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

»

[PATCH] Demonstrate failing rtstring ctor

Submitted by peter on Wed, 2010-10-20 21:12.

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

»

[PATCH] Demonstrate failing rtstring ctor

Submitted by peter on Wed, 2010-10-20 20:40.

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

»

[PATCH] Demonstrate failing rtstring ctor

Submitted by peter on Wed, 2010-10-20 20:08.

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

»

[PATCH] Demonstrate failing rtstring ctor

Submitted by peter on Wed, 2010-10-20 19:36.

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

»

[PATCH] Demonstrate failing rtstring ctor

Submitted by peter on Wed, 2010-10-20 19:04.

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

»

[PATCH] Demonstrate failing rtstring ctor

Submitted by peter on Wed, 2010-10-20 18:32.

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

»

[PATCH] Demonstrate failing rtstring ctor

Submitted by peter on Wed, 2010-10-20 18:00.

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

»

[PATCH] Demonstrate failing rtstring ctor

Submitted by peter on Wed, 2010-10-20 17:28.

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

»

[PATCH] Demonstrate failing rtstring ctor

Submitted by peter on Wed, 2010-10-20 16:56.

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

»

[PATCH] Demonstrate failing rtstring ctor

Submitted by peter on Wed, 2010-10-20 16:24.

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

»

[PATCH] Demonstrate failing rtstring ctor

Submitted by peter on Wed, 2010-10-20 15:52.

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

»

[PATCH] Demonstrate failing rtstring ctor

Submitted by peter on Wed, 2010-10-20 15:20.

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

»

[PATCH] Demonstrate failing rtstring ctor

Submitted by peter on Wed, 2010-10-20 14:52.

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

»

[PATCH] Demonstrate failing rtstring ctor

Submitted by peter on Wed, 2010-10-20 14:24.

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

»

[PATCH] Demonstrate failing rtstring ctor

Submitted by peter on Wed, 2010-10-20 13:56.

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

»

[PATCH] Demonstrate failing rtstring ctor

Submitted by peter on Wed, 2010-10-20 13:28.

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

»

[PATCH] Demonstrate failing rtstring ctor

Submitted by peter on Wed, 2010-10-20 13:00.

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

»

[PATCH] Demonstrate failing rtstring ctor

Submitted by peter on Wed, 2010-10-20 12:32.

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

»

[PATCH] Demonstrate failing rtstring ctor

Submitted by peter on Wed, 2010-10-20 12:04.

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

»

[PATCH] Demonstrate failing rtstring ctor

Submitted by peter on Wed, 2010-10-20 11:36.

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

»

[PATCH] Demonstrate failing rtstring ctor

Submitted by peter on Wed, 2010-10-20 11:08.

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

»

[PATCH] Demonstrate failing rtstring ctor

Submitted by peter on Wed, 2010-10-20 10:40.

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

»

[PATCH] Demonstrate failing rtstring ctor

Submitted by peter on Wed, 2010-10-20 10:12.

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

»

[PATCH] Demonstrate failing rtstring ctor

Submitted by peter on Wed, 2010-10-20 09:44.

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

»

[PATCH] Demonstrate failing rtstring ctor

Submitted by peter on Wed, 2010-10-20 09:16.

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

»

[PATCH] Demonstrate failing rtstring ctor

Submitted by peter on Wed, 2010-10-20 08:48.

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

»

[PATCH] Demonstrate failing rtstring ctor

Submitted by peter on Wed, 2010-10-20 08:20.

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

»

[PATCH] Demonstrate failing rtstring ctor

Submitted by peter on Wed, 2010-10-20 07:52.

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

»

[PATCH] Demonstrate failing rtstring ctor

Submitted by peter on Wed, 2010-10-20 07:24.

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

»

[PATCH] Demonstrate failing rtstring ctor

Submitted by peter on Wed, 2010-10-20 06:56.

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

»

[PATCH] Demonstrate failing rtstring ctor

Submitted by peter on Wed, 2010-10-20 06:28.

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

»