Re: [HACKERS] PL code and fmgr_addr

>
> Another problem I found with the PL code was that it took the fmgr()
> macro, and made it call a function call to fmgr_addr, which just killed
> performance.
>
> I made fmgr_addr() a macro too.
>
> --
> Bruce Momjian
> maillist@candle.pha.pa.us
>
>

    Just to let you know - after fixing some other problems
    caused by the bpchar trouble my PLtcl tests went through
    again. Looks the macroization is O.K.


Until later, Jan

--

#======================================================================#
# It's easier to get forgiveness for being wrong than for being right. #
# Let's break this rule - forgive me.                                  #
#======================================== jwieck@debis.com (Jan Wieck) #