> To answer another misconception that I saw in this thread: > > : The old language names "internal" and "C" will continue to refer to > : functions with the old calling convention. We should deprecate > : old-style functions because of their portability problems, but the > : support for them will only be one small function handler routine, > : so we can leave them in place for as long as necessary. My question is can we drop newC and use just plain C in 7.2 or 7.3? -- Bruce Momjian | http://candle.pha.pa.us [EMAIL PROTECTED] | (610) 853-3000 + If your life is a hard drive, | 830 Blythe Avenue + Christ can be your backup. | Drexel Hill, Pennsylvania 19026
- AW: [HACKERS] Coping with 'C' vs 'newC' function la... Zeugswetter Andreas SB
- Re: [HACKERS] Coping with 'C' vs 'newC' functi... Marko Kreen
- AW: [HACKERS] Coping with 'C' vs 'newC' functi... Zeugswetter Andreas SB
- Re: [HACKERS] Coping with 'C' vs 'newC' fu... 'Marko Kreen'
- Re: [HACKERS] Coping with 'C' vs 'newC... mlw
- Re: [HACKERS] Coping with 'C' vs '... Tom Lane
- Re: [HACKERS] Coping with 'C'... Bruce Momjian
- Re: [HACKERS] Coping with... Philip Warner
- Re: [HACKERS] Coping ... Ross J. Reedstrom
- Re: [HACKERS] Coping ... 'Marko Kreen'
- Re: [HACKERS] Coping ... Don Baccus
- Re: [HACKERS] Coping ... Ross J. Reedstrom
- AW: [HACKERS] Coping with 'C' vs 'newC' functi... Zeugswetter Andreas SB
- AW: [HACKERS] Coping with 'C' vs 'newC' functi... Zeugswetter Andreas SB