Do we want the opcode to be so complicated? I thought we are going to use this kind of thing for generic pointers. The "p" member of opcode does not make any sense to me. Hong > Earlier there was some discussion about changing typedef long IV > to > typedef union { > IV i; > void* p; > } opcode_t;
- [PATCH] changing IV to opcode_t!! Gibbs Tanton - tgibbs
- Re: [PATCH] changing IV to opcode_t!! Simon Cozens
- RE: [PATCH] changing IV to opcode_t!! Gibbs Tanton - tgibbs
- Re: [PATCH] changing IV to opcode_t!! Hong Zhang
- Re: [PATCH] changing IV to opcode_t!! Jarkko Hietaniemi
- RE: [PATCH] changing IV to opcode_t!! Gibbs Tanton - tgibbs
- RE: [PATCH] changing IV to opcode_t!! Dan Sugalski
- Re: [PATCH] changing IV to opcode_t!! Simon Cozens
- RE: [PATCH] changing IV to opcode_t!! Gibbs Tanton - tgibbs
- Re: [PATCH] changing IV to opcode_t!! Dan Sugalski
- RE: [PATCH] changing IV to opcode_t!! Andy Dougherty
- RE: [PATCH] changing IV to opcode_t!! Brent Dax
- RE: [PATCH] changing IV to opcode_t!! Brent Dax