> - do we expect to have more then 32 different classes? > i see 13 operator classes currently, though my tree may be out of date
> A perl script that scans ops-files for opcode classes and spits out: > > a) a pod with opcode classes headings and the list of opcodes that > belong to that class (at best created from a template, which has some > more explanation to that stuff) > the attached tarfile contains a script (tools/docs/opslist.pl) should generate a file, docs/ops/opslist.pod, with the above information > b) a C include file that defines bitmask enums for the > classes plus some > common shortcuts comming from a config file. These enums > should then be > scanned during Configure and provide a user visible PASM in > runtime/parrot/include. > If we have more then 32 classes, we'll use a ParrotSet PMC > (which will > be handy anyway) > i'm not sure where to get the info i need to do this. hope the attached script helps. > leo > --jerry ************************************************************************** This e-mail and any files transmitted with it may contain privileged or confidential information. It is solely for use by the individual for whom it is intended, even if addressed incorrectly. If you received this e-mail in error, please notify the sender; do not disclose, copy, distribute, or take any action in reliance on the contents of this information; and delete it from your system. Any other use of this e-mail is prohibited. Thank you for your compliance.
opsfile.tgz
Description: Binary data
