Return to BSD News archive
Path: sserve!manuel!munnari.oz.au!spool.mu.edu!yale.edu!ira.uka.de!news.belwue.de!news.uni-tuebingen.de!mailserv!zxmsd01 From: zxmsd01@mailserv.zdv.uni-tuebingen.de (Gunther Schadow) Newsgroups: comp.unix.bsd Subject: 386BSD: floatingpoint conversion? [efg]cvt()/[efg]convert() missing Message-ID: <zxmsd01.711064103@mailserv> Date: 13 Jul 92 21:48:23 GMT Article-I.D.: mailserv.zxmsd01.711064103 Sender: news@softserv.zdv.uni-tuebingen.de (News Operator) Organization: Comp. Center (ZDV) U of Tuebingen, FRG Lines: 27 After I experienced that the library of BSD is subject to change (regarding ftime() gtty() etc.), I wonder whether floating point conversions in general are obsolete now too :-). For the porting of ingres I missed the functions: char *ecvt(double, int, int *, int *) and char *fcvt(double, int, int *, int *). In the manual of SUN-OS I found that the [efg]cvt() functions are obsolete and replaced by [efg]convert(). But there isn't any *convert in the library of 386bsd nor are there any functions to convert floating point to ASCII exept the *printf() group. So I hacked something similar with sprintf(). I think it would be rather straitforward to pass the precision parameter directly to the converting function instead of hacking a format string from it to be again passed to sprintf. Any ideas, why we don't have any appropriate function and what we can do about it? regards -Gunther -- ------------------------------------------------------------------------------- Gunther Schadow, e-mail: Gunther@mailserv.ZDV.Uni-Tuebingen.DE Sudetenstrasse 25, Phone: (49) 7071/37527 7400 Tuebingen, Germany.__________Stop__________Horn Please!__________O.K. TATA