Hi, On Tuesday 23 March 2004 14:49, Gay, Jerry wrote: > > - do we expect to have more then 32 different classes? > > i see 13 operator classes currently, though my tree may be out of date I think we should limit the number of unique IDs available at runtime to 32. We can assign the same number to several symbolic names (maybe even on demand, at runtime). This way, one can at least query if a specific feature is enabled. We then have "meta groups", for example a single "math" group instead of base_math and advanced_math; I think it is harmless if enabling one feature does also enable another (related) feature.
A fine graded OP classification can be a win, but it is not necessary to be able to play around with 100000 different hints _at runtime_. If hints can be freely grouped (at compiletime), everyone should be able to get a parrot that fulfils even very specific needs. Hints should IMO only be used to control parrot's core OPs. Extensions (i.e. special RE ops) can be controlled by restrictions at loadtime. > > 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 I belive Leo meant the hint classes, base_core and base_network for example. > > 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. lib/Parrot/OpLib/core.pm > hope the attached script helps. The list looks okay, maybe it can be kept as an additional section. Another section should show all hint groups and the OPs that belong to this list. A simple list is included in my previous mail from yesterday. > > leo > > --jerry jens
