WDX: Integral data types

tbeu · Post by *tbeu » 2011-09-27, 20:38 UTC

The content plugin API currently allows only 32-bit and 64-bit signed integers for integral data types of content fields.

Code: Select all

#define ft_numeric_32 1
#define ft_numeric_64 2

Would it be possible to also add 8-bit and 16-bit integers and all their unsigned equivalents? This would complete the API.

Post by *ghisler(Author) » 2011-09-28, 00:52 UTC

Currently this isn't planned, so the compatibility with older TC versions isn't broken. There wouldn't be any big benefit, since all the smaller numbers can be represented by the larger ones (except for 64-bit unsigned).

tbeu · Post by *tbeu » 2012-01-24, 16:17 UTC

Plugin compatibilty should not be a problem if you increase the interface version and the WDX developer checks it in ContentSetDefaultParams. Thus, newer plugin versions should work with old versions of TC.

MVV · Post by *MVV » 2012-01-25, 18:20 UTC

Why don't you want to use 32-bit integers instead?

(3-bit was a misprint)

tbeu · Post by *tbeu » 2012-01-26, 07:49 UTC

MVV wrote:Why don't you want to use 3-bit integers instead?

Because I do not use them very often. Do you?

MVV · Post by *MVV » 2012-01-26, 09:13 UTC

I don't return such small numbers in my plugins so it's not a problem for me. But I would return 8- or 16-bit integers with ft_numeric_32 type if I needed it. All your plugin needs is to pass number to TC, so it doesn't matter it is 8-bit or 32-bit.