[kepler-dev] Byte type in Kepler/Ptolemy.

[Jianwu Wang]

Hi Christopher,

     Thanks. I'll add one to Ptolemy if we need to.

Best wishes

Sincerely yours

Jianwu Wang, Ph.D.
jianwu at sdsc.edu
http://users.sdsc.edu/~jianwu/

Assistant Project Scientist
Scientific Workflow Automation Technologies (SWAT) Laboratory
San Diego Supercomputer Center
University of California, San Diego
San Diego, CA, U.S.A.

On 2/20/13 5:48 PM, Christopher Brooks wrote:
> Hi Jianwu,
> Sure, if you want a ByteToken, feel free to add it to the ptII tree.
> Be sure that the code closely follows the coding standard.
> Be sure to add unit tests.
>
> data/UnsignedByteToken.java says:
>>  A token that contains a byte number in the range 0 through 255. This
>>  UnsignedByteToken definition is in contrast to Java's definition of a
>>  byte as a number in the range -128 through 127.
>
> A ByteToken and an UnsignedByteToken are not losslessly convertible to 
> each other.
>
> _Christopher
>
>
> On 2/13/13 4:28 PM, Jianwu Wang wrote:
>> Hi,
>>
>>     Kepler and Ptolemy support many types including unsignedByte. But 
>> I didn't see normal byte in Ptolemy. From the implementation of 
>> UnsignedByteToken, it looks we can use it for normal byte through its 
>> function like UnsignedByteToken(byte) and byteValue(). But I still 
>> think it is valuable to have a separate Byte type in Ptolemy. Any 
>> opinion on it? Thanks.
>>
>