Leopold Toetsch <[EMAIL PROTECTED]> writes: > I alread did ask some time ago:
I looked up the original thread: (date 13.02.03) http://groups.google.de/groups?hl=de&lr=&ie=UTF-8&th=53f5dbdd508603fb&rnum=1 > Is there any compelling reason that *_keyed_int vtables like: > > PMC* get_pmc_keyed_int (INTVAL* key) > > take a pointer to the key? Symetry with the multi_keyed case. But quoting form the cited thread: LT> We can't do these multi_keyed ops in that way. After this the thread died. > This needs then (in all ops files, incl JIT): > > INTVAL key = $3; > $1 = $2->vtable->get_pmc_keyed_int(interpreter, $2, &key); > > (setting up a local and passing the address of it) > > Just passing the integer key would be shorter and faster. > leo This is a good idea, and I support it. (As I already said in Febuary) boe -- Juergen Boemmels [EMAIL PROTECTED] Fachbereich Physik Tel: ++49-(0)631-205-2817 Universitaet Kaiserslautern Fax: ++49-(0)631-205-3906 PGP Key fingerprint = 9F 56 54 3D 45 C1 32 6F 23 F6 C7 2F 85 93 DD 47