ppdefs

typefld

mapfld (in_value, in_key, out_key)

Map a given source field to the corresponding target field by querying the type hash. This gives you a way to say, "Find the type whose $in_key is equal to $value, and return that type's value for $out_key. For example:

typesynonyms

return type related synonym definitions to be included in pdl.h . This routine must be updated to include new types as required. Mostly the automatic updating should take care of the vital things.

datatypes_header

return C header text for pdl.h and pdlsimple.h.

PDL::Type OBJECTS

This module declares one class - PDL::Type - objects of this class are returned by the type method of a piddle. It has several methods, listed below, which provide an easy way to access type information:

Additionally, comparison and stringification are overloaded so that you can compare and print type objects, e.g.

The default special numerical value used to represent bad values for this type. (You can change the value that represents bad values for each type during runtime.) See the orig_badvalue routine in PDL::Bad for more details.

Adding/removing types

You can change the types that PDL knows about by editing entries in the definition of the variable @types that appears close to the top of the file Types.pm.PL (i.e. the file from which this module was generated).

Format of a type entry

Each entry in the @types array is a hash reference. Here is an example taken from the actual code that defines the ushort type:

Before we start to explain the fields please take this important message on board: entries must be listed in order of increasing complexity. This is critical to ensure that PDL's type conversion works correctly. Basically, a less complex type will be converted to a more complex type as required.

Fields in a type entry

Each type entry has a number of required and optional entry.

A list of all the entries:

identifier

Required. A short sequence of upercase letters that identifies this type uniquely. More than three characters is probably overkill.

onecharident

Optional. Only required if the identifier has more than one character. This should be a unique uppercase character that will be used to reference this type in PP macro expressions of the TBSULFD type. If you don't know what I am talking about read the PP manpage or ask on the mailing list.

pdlctype

Required. The typedefed name that will be used to access this type from C code.

realctype

Required. The C compiler type that is used to implement this type. For portability reasons this one might be platform dependent.

ppforcetype

Required. The type name used in PP signatures to refer to this type.

usenan

Required. Flag that signals if this type has to deal with NaN issues. Generally only required for floating point types.

packtype

Required. The Perl pack type used to pack Perl values into the machine representation for this type. For details see perldoc -f pack.

Also have a look at the entries at the top of Types.pm.PL.

The syntax is not written into stone yet and might change as the concept matures.

Other things you need to do

You need to check modules that do I/O (generally in the IO part of the directory tree). In the future we might add fields to type entries to automate this. This requires changes to those IO modules first though.

You should also make sure that any type macros in PP files (i.e. $TBSULFD...) are updated to reflect the new type. PDL::PP::Dump has a mode to check for type macros requiring updating. Do something like