But this would also cause problem in the old version of tgif. This is especially true in the state(...) line because now it has one extra field!
--Bill On Mon, Sep 6, 2010 at 2:46 PM, Carlo Segre <se...@iit.edu> wrote: > > Sorry about answering myself. I see the problem. In the older version it > is likely that the -D_NO_LOCALE_SUPPORT was used or there was no locale > support so that the old files Gunter has contain the decimal points while > files he is writing out now have the comma. The new version of the program > chokes on a decimal point when reading in files. This is serious and needs > to be fixed. I will look into it ASAP. > > Carlo > > > > On Mon, 6 Sep 2010, Carlo Segre wrote: > > >> Hi >> >> On Mon, 6 Sep 2010, Bill Cheng wrote: >> >> >>> I'm not sure exactly how to fix this bug since I'm not too familiar with >>> the localization stuff. I thought the locale should be set correctly due to >>> the call to setlocale(LC_ALL, "C") in tgif. But this code can be skipped if >>> -D_NO_LOCALE_SUPPORT compiler flag is used. The _NO_LOCALE_SUPPORT compiler >>> flag should only be used on a system that does not have the setlocale() >>> function. But anyone can just use -D_NO_LOCALE_SUPPORT to compile tgif. Is >>> there a way you can find of if -D_NO_LOCALE_SUPPORT was used to compile >>> tgif? >>> >>> >> It is likely that the -D_NO_LOCALE_SUPPORT flag was not used as >> localization is important in Debian. I will check into it. Do you have any >> idea why this problem was not evident in the older version 4.1.45? >> >> I believe that Günter has been using tgif for some time and clearly his >> saved files have the comma but he had no problems with previous versions. >> >> Carlo >> >> >> > -- > Carlo U. Segre -- Professor of Physics > Associate Dean for Graduate Admissions, Graduate College > Illinois Institute of Technology > Voice: 312.567.3498 Fax: 312.567.3494 > se...@iit.edu http://www.iit.edu/~segre <http://www.iit.edu/%7Esegre> > se...@debian.org >
