Two patches that improve the ros-primitives typekit. Some code in OCL assumes
int32 and uint32 are convertible, this led to incomplete printing of a type's
contents in the taskbrowser when the ros-primitives typekit was loaded. These
conversions and lot of others are added with this patch.
You might consider splitting this typekit in 2 parts, since it takes about
2.2GB RAM to compile this file.
Peter
| Attachment | Size |
|---|---|
| 0002-ros-primitives-define-automatic-manual-conversions.patch | 7.02 KB |
| 0001-ros-primitives-use-StdTypeInfo-instead-of-low-level-.patch | 3.13 KB |
rtt_ros_integration: typekit updates
2010/12/17 Peter Soetens <peter [..] ...>:
> Two patches that improve the ros-primitives typekit. Some code in OCL assumes
> int32 and uint32 are convertible, this led to incomplete printing of a type's
> contents in the taskbrowser when the ros-primitives typekit was loaded. These
> conversions and lot of others are added with this patch.
>
> You might consider splitting this typekit in 2 parts, since it takes about
> 2.2GB RAM to compile this file.
I've splitted this patch in multiple files and added array support for
the ros primitive types. I notice that some types don't get displayed
well in the taskbrowser, e.g.
Deployer [S]> var Int32 t
= {data = 0 }
Deployer [S]> var UInt8 p
= {data = }
Any idea what might cause this?
Steven
>
> Peter
>
rtt_ros_integration: typekit updates
On Sun, Dec 19, 2010 at 2:46 PM, Steven Bellens
<steven [dot] bellens [..] ...> wrote:
> 2010/12/17 Peter Soetens <peter [..] ...>:
>> Two patches that improve the ros-primitives typekit. Some code in OCL assumes
>> int32 and uint32 are convertible, this led to incomplete printing of a type's
>> contents in the taskbrowser when the ros-primitives typekit was loaded. These
>> conversions and lot of others are added with this patch.
>>
>> You might consider splitting this typekit in 2 parts, since it takes about
>> 2.2GB RAM to compile this file.
>
> I've splitted this patch in multiple files and added array support for
> the ros primitive types. I notice that some types don't get displayed
> well in the taskbrowser, e.g.
>
> Deployer [S]> var Int32 t
> = {data = 0 }
>
> Deployer [S]> var UInt8 p
> = {data = }
>
> Any idea what might cause this?
I have noticed the same. I think it's because the value is 'null'
('\0'). We could print this kind of data in hex (0x00) to avoid such
unriendly readouts. Or catch it in the TaskBrowser and pretty-print it
there.
Peter
--
Orocos-Dev mailing list
Orocos-Dev [..] ...
http://lists.mech.kuleuven.be/mailman/listinfo/orocos-dev
rtt_ros_integration: typekit updates
2010/12/17 Peter Soetens <peter [..] ...>
> Two patches that improve the ros-primitives typekit. Some code in OCL
> assumes
> int32 and uint32 are convertible, this led to incomplete printing of a
> type's
> contents in the taskbrowser when the ros-primitives typekit was loaded.
> These
> conversions and lot of others are added with this patch.
>
> You might consider splitting this typekit in 2 parts, since it takes about
> 2.2GB RAM to compile this file.
>
x-(
>
> Peter
>
> --
> Orocos-Dev mailing list
> Orocos-Dev [..] ...
> http://lists.mech.kuleuven.be/mailman/listinfo/orocos-dev
>
>