[Top][All Lists]

[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]

[Pspp-commits] [SCM] GNU PSPP branch, value-rep, updated. v0.6.1-617-gc6

From: Ben Pfaff
Subject: [Pspp-commits] [SCM] GNU PSPP branch, value-rep, updated. v0.6.1-617-gc6c43bb
Date: Tue, 12 May 2009 03:09:26 +0000

This is an automated email from the git hooks/post-receive script. It was
generated because a ref change was pushed to the repository containing
the project "GNU PSPP".

The branch, value-rep has been updated
       via  c6c43bb50c5ee662b86ba74b0d3e3a58c09dd509 (commit)
      from  766d768447de777a99a08ab064892676ada10a71 (commit)

Those revisions listed above that are new to this repository have
not appeared on any other notification email; so we list those
revisions in full, below.

- Log -----------------------------------------------------------------
commit c6c43bb50c5ee662b86ba74b0d3e3a58c09dd509
Author: Ben Pfaff <address@hidden>
Date:   Mon May 11 20:08:19 2009 -0700

    Make value_set_missing(), etc. tolerate values of width -1.
    In some circumstances a value of width -1 crops up, e.g. when a case is
    made from a dictionary that has had a variable deleted in the middle.
    Such a value has no content at all.  In the long run it should be possible
    to get rid of these values entirely--their presence is a wart--but for now
    the case and value code needs to tolerate them.
    This fixes a segfault in the GUI when inserting a new case when the
    datasheet case has a column with width -1 (due to deletion of a variable),
    which was caused by case_set_missing() calling value_set_missing() for
    the -1 width variable, which in turn was writing through an invalid


Summary of changes:
 src/data/value.c |   23 +++++++++++++----------
 1 files changed, 13 insertions(+), 10 deletions(-)


reply via email to

[Prev in Thread] Current Thread [Next in Thread]