On Sat, Oct 30, 2004 at 03:05:02PM +0200, Martin Stjernholm, Roxen IS @ Pike developers forum wrote:
How is it in lpc?
the psyc guys are working on a test case, from what i can gather it may be getting more complex.
from ldmud lang.y:
/* This is used to parse and return the indexing operation * of an array or mapping. * .inst gives the type of the operation: * F_INDEX: [x] * F_RINDEX: [<x] * F_AINDEX: [>x] * F_RANGE: [ x.. y] * F_RN_RANGE: [<x.. y] * F_NR_RANGE: [ x..<y] * F_RR_RANGE: [<x..<y] * F_AN_RANGE: [>x.. y] * F_AR_RANGE: [>x..<y] * F_NA_RANGE: [ x..>y] * F_RA_RANGE: [<x..>y] * F_AA_RANGE: [>x..>y] * F_NX_RANGE: [ x.. ] * F_RX_RANGE: [<x.. ] * F_AX_RANGE: [>x.. ] * .start and .end are the bytecode limits of the whole * operation. * .type1 and optionally .type2 are the types of the * index values. */
[>x] appears to be the same as [x], so unless full lpc compatibility is the goal, this can be ignored.
greetings, martin.