Re: PSPP-BUG: Bug

De: John Darrington <john@darrington.wattle.id.au>
Enviado: martes, 16 de marzo de 2021 0:41
Para: KATIUSKA KRUSCAYA KING MANTILLA <kkking@uce.edu.ec>
Cc: bug-gnu-pspp@gnu.org <bug-gnu-pspp@gnu.org>
Asunto: Re: PSPP-BUG: Bug

Thank you for the bug report.

A number of Windows users have reported this problem.

1. It seems to only effect Windows. So the easiest way to work around the
   issue is to use another system (eg GNU/Linux) instead of Windows. PSPP
   runs best on GNU.

2. This stray null character can be ignored. It is cosmetically non-ideal but
   doesn't affect the accuracy of the output.

3. So far, I haven't been able to reproduce the issue. Can somebody show me a
   *complete* syntax which reproduces this. A complete syntax must start with
   NEW FILE.   If we can reliably reproduce the problem, then we have a chance
   of fixing it.

J'

On Tue, Mar 16, 2021 at 03:58:38AM +0000, KATIUSKA KRUSCAYA KING MANTILLA via Bug-gnu-pspp wrote:
     Good night,


     When some of my students run PSPP 1.4.1-g79ad47 on Windows 8.1 Pro system and Windows 7 Starter system, executing the following syntax:



     COMPUTE HACINAM = TP1/H01.

     EXECUTE.

     COMPUTE HOGASIG = HACINAM >3.

     EXECUTE.



     FREQUENCIES

                 /VARIABLES=HOSASIG

                 /FORMAT=AVALUE TABLE.



     In the results they have an unreadable character that I think should be the number 0.


     How can I help them to fix this error?


     Best regards,

     Katiuska King
     Docente - Investigadora
     Facultad de Ciencias Sociales y Humanas (FCSH)
     Universidad Central del Ecuador

     _______________________________________________
     Bug-gnu-pspp mailing list
     Bug-gnu-pspp@gnu.org
     https://lists.gnu.org/mailman/listinfo/bug-gnu-pspp

From:	KATIUSKA KRUSCAYA KING MANTILLA
Subject:	Re: PSPP-BUG: Bug
Date:	Sat, 17 Apr 2021 16:18:54 +0000