bugPSPP - Bugs: bug #30693, MXWARNS=0 should be implemented

 
 

bug #30693: MXWARNS=0 should be implemented

Submitter:  Ben Pfaff <blp>
Submitted:  Sun 08 Aug 2010 08:14:03 PM UTC
   
 
Category:  Syntax Parser Severity:  5 - Average
Status:  Fixed Assigned to:  None
Open/Closed:  Closed Release:  None
Effort:  0.00
* Mandatory Fields

Add a New Comment Rich Markup
   

Sun 22 Aug 2010 10:52:29 AM UTC, comment #2: 

I pushed a fix for this.

John Darrington <jmd>
Group administrator
Tue 10 Aug 2010 06:14:02 PM UTC, comment #1: 

From: "la" <la@jump23.com>

> Setting maxwarns to a large number presents a different problem.  My file is
> well over 255 million records and pspp generates a error statement for each
> record/variable that contains blanks if it's defined as numeric. So the pspp
> would generate an enormous report.
>
> I tried using SET BLANKS=0 or other data transformation to convert blanks to
> 0 within my pspp syntax file but it seems that the error is generated as
> soon as it reads the data before anything else happens.  Does this mean that
> I have to first process the file outside of pspp to convert blanks to 0?


Ben Pfaff <blp>
Group administrator
Sun 08 Aug 2010 08:14:03 PM UTC, original submission:  

SET MXWARNS=0 is supposed to suppress all warnings, except for a single warning that additional warnings have been suppressed.  We should implement this.

Ben Pfaff <blp>
Group administrator

 

(Note: upload size limit is set to 16384 kB, after insertion of the required escape characters.)

Attach Files:
   
   
Comment:
   

No files currently attached

 

Depends on the following items: None found

Items that depend on this one: None found

 

Carbon-Copy List
  • -email is unavailable- added by jmd (Posted a comment)
  • -email is unavailable- added by blp (Submitted the item)
  • -email is unavailable- added by blp
  •  

    There are 0 votes so far. Votes easily highlight which items people would like to see resolved in priority, independently of the priority of the item set by tracker managers.

    Only logged-in users can vote.

     

    Follow 4 latest changes.

    Date Changed by Updated Field Previous Value => Replaced by
    2010-08-22 jmd StatusConfirmed Fixed
        Open/ClosedOpen Closed
    2010-08-08 blp SummaryMXWARNS=0 should be implemente MXWARNS=0 should be implemented
    2010-08-08 blp Carbon-Copy- Added -email is unavailable-

    Back to the top

    Powered by Savane 3.13-4448.
    Corresponding source code