(
Jump to the original submission)
Tue 31 Mar 2009 08:03:54 AM UTC, comment #7:
I've merged the stable branch into master so it should be there now.
|
Tue 31 Mar 2009 05:37:40 AM UTC, comment #6:
I've found this problem on master. Can you add this patch to master also?
Thanks!
|
Tue 31 Mar 2009 05:32:45 AM UTC, comment #5:
Checked in to stable.
|
Tue 31 Mar 2009 04:45:32 AM UTC, comment #4:
>I suggest the attached patch be checked in to stable.
Good catch. Please check this in.
|
Tue 31 Mar 2009 03:13:55 AM UTC, comment #3:
The problem seems to be that SYSMIS values are supposed to be represented "." but we've been writing them "./"
I suggest the attached patch be checked in to stable.
(file #17843)
|
Sat 28 Mar 2009 05:42:49 AM UTC, comment #2:
I guess that pspp doesn't uses the extension of the file to figure out what is its format. That's why I save it as .sav and it works.
I've discovery that if I put an (ELSE = 0) it works.
|
Sat 28 Mar 2009 05:28:51 AM UTC, comment #1:
Files generated by EXPORT normally take the suffix .por
Despite that, this bug report still seems to have highlighted a problem.
|
Sat 28 Mar 2009 05:10:50 AM UTC, original submission:
If you create a simple file with only one variable with values from 1 to 10 (like the attached) and run the syntax above on pspp, the out.sav file isn't readable by pspp.
GET
/FILE=test.sav.
RECODE test1 (1 = 1) INTO cor1.
EXECUTE.
EXPORT
/OUTFILE=out.sav.
|
(Note: upload size limit is set to 16384 kB, after insertion of the required
escape characters.)
Attach File(s):
Comment:
Depends on the following items: None found
Items that depend on this one: None found
Follow 8 latest changes.