I would kill it. FPBUF_SIZE and DMAXEXP can go too.
On Fri, Sep 11, 2015 at 11:41:40PM -0400, Michael McConville wrote: > Michael McConville wrote: > > FP has been undefined for at least ten years, and probably forever. > > It's used to conditionally add two small sections and one large > > section of shf.c. > > > > My initial reaction is that FP should be removed. Is there any reason > > to keep it? Should the associated code stay or go? > > To be (far) more specific, it's used to enable the 'e', 'g', and 'f' > fields of ksh's vfprintf() clone. On one hand, this can't be too > important if it was disabled for >10 years. On the other, the code at > least compiles... > > It seems that there's a lot of good cleanup to be done in ksh. There are > many hacks and reimplementations that seem to be remnants of a time when > you couldn't rely on standards much. >
