IRTGs currently cannot contain negative weights when constructing with an IrtgInputCodec. It expects:
NUMBER : [0-9.] ([0-9.eE-]*);
...
weight : '[' NUMBER ']';
I guess nobody ever wanted negative weights and therefore just did not think about negative weights. Is there another reason for only accepting positive weights or can I extend it for negative ones?
IRTGs currently cannot contain negative weights when constructing with an IrtgInputCodec. It expects:
I guess nobody ever wanted negative weights and therefore just did not think about negative weights. Is there another reason for only accepting positive weights or can I extend it for negative ones?