On Tuesday 18 September 2001 03:55 pm, Dan Sugalski wrote:
> One of the things that the configure script needs to do is generate the
> opcode dispatch macro to either be a giant switch statement (with a
> fallthrough default to handle cases we don't know about) or the function
> table dispatch we
Simon Cozens:
# On Tue, Sep 18, 2001 at 02:51:35PM -0700, Brent Dax wrote:
# > So, something more like this?
#
# Urh, how can I put this? No.
#
# I *really* want to avoid macro hackery - undef'ing this and
# then testing if it's defined and then redefining it, and
# urgh, urgh, urgh. No.
#
# I was
On Tue, Sep 18, 2001 at 02:51:35PM -0700, Brent Dax wrote:
> So, something more like this?
Urh, how can I put this? No.
I *really* want to avoid macro hackery - undef'ing this and
then testing if it's defined and then redefining it, and
urgh, urgh, urgh. No.
I was thinking more like:
> +++ bu
Simon Cozens:
# On Tue, Sep 18, 2001 at 02:32:32PM -0700, Brent Dax wrote:
# > If somebody codes up the alternate dispatch, I can easily modify
# > Configure.pl, config_h.in and the hints files to handle it.
# Something
# > like this, perhaps:
#
# Something like that, but the Right Way would be t
On Tue, Sep 18, 2001 at 02:32:32PM -0700, Brent Dax wrote:
> If somebody codes up the alternate dispatch, I can easily modify
> Configure.pl, config_h.in and the hints files to handle it. Something
> like this, perhaps:
Something like that, but the Right Way would be to rewrite DO_OP in
interp_g
