Changes between Initial Version and Version 1 of Ticket #1500

Show
Ignore:
Timestamp:
04/21/10 08:26:17 (4 years ago)
Author:
dukeleto
Comment:

Legend:

Unmodified
Added
Removed
Modified
  • Ticket #1500

    • Property priority changed from normal to major
  • Ticket #1500 – description

    initial v1  
    1212It is defined to be in the "filesys_open" opcode group. Currently there is no way to tell if a certain opcode is in a given group. The information does not seem to make it into op_info_t, but it is in lib/Parrot/OpLib/core.pm . I propose a public C API that will consist of at least these three functions: 
    1313 
    14 {{{ Parrot_opcode_is_in_group(string opcode_name, string group_name) }}} 
     14{{{ Parrot_sec_opcode_is_in_group(string opcode_name, string group_name) }}} 
    1515 
    1616This function would take an opcode name and opcode group name as argument and return true if the opcode is in the group, false otherwise. 
    1717 
    18 {{{ Parrot_opcodes_in_group(string opcode_group) }}} 
     18{{{ Parrot_sec_opcodes_in_group(string opcode_group) }}} 
    1919 
    2020This function takes a string argument of an opcode group name and returns a ResizableStringArray containing all opcodes in that group. 
    2121 
    22 {{{ Parrot_groups_containing_opcode(string opcode_name) }}} 
     22{{{ Parrot_sec_groups_containing_opcode(string opcode_name) }}} 
    2323 
    2424This function takes a string argument of an opcode name and returns a ResizableStringArray listing all groups that contain the given opcode name.