[Pspp-commits] [SCM] GNU PSPP branch, value-rep, created. v0.6.1-563-gf3e9fce

[Ben Pfaff]

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 created
        at  f3e9fcee702b4b6d0633ad9568f4ae660a3fc294 (commit)

- Log -----------------------------------------------------------------
commit f3e9fcee702b4b6d0633ad9568f4ae660a3fc294
Author: Ben Pfaff <address@hidden>
Date:   Wed Apr 15 22:31:56 2009 -0700

    perl-module: Better document "make test" requirements.

commit 12f6607eaebb52f9b99732386cad425ba200c746
Author: Ben Pfaff <address@hidden>
Date:   Tue Mar 31 22:00:44 2009 -0700

    Delete CORRELATIONS skeletal parser.
    
    This code didn't do anything useful, it just parsed syntax.  We can
    resurrect it when someone wants to implement CORRELATIONS later.

commit a7919d1f5d2baf6fa320849a898471c2dad56092
Author: Ben Pfaff <address@hidden>
Date:   Sun Mar 29 22:53:07 2009 -0700

    Change "union value" to dynamically allocate long strings.
    
    Until now, a single "union value" could hold a numeric value or a short
    string value.  A long string value (one longer than MAX_SHORT_STRING)
    required a number of contiguous "union value"s.  This situation was
    inconvenient sometimes, because any occasion where a long string value
    might be required (even if it was unlikely) required using dynamic
    memory allocation.
    
    With this change, a value of any type, regardless of whether it is numeric
    or short or long string, occupies a single "union value".  The internal
    representation of short and long strings is now different, however: long
    strings are now internally represented by a pointer to dynamically
    allocated memory.  This means that "union value"s must now be initialized
    and uninitialized properly, to ensure that memory is properly allocated
    and freed behind the scenese.
    
    This change thus has a ripple effect on PSPP code that works with values.
    In particular, code that deals with cases is greatly changed, because a
    case now needs to know the type of each value that it contains.  Thus, a
    new concept called a "case prototype", which represents the type and
    width of each value within a case, is introduced, and every place in PSPP
    that creates a case must now create a corresponding prototype to go with
    it.
    
    This commit is not cleaned up to production standards.  It needs
    additional work on comments, for example, as well as updates to the
    developers' reference.  There might be unrelated debug prints still left
    in, and so on.  Nevertheless it should serve as a place to start
    discussion.

commit f4ff12df5897edfc694eae0b81fb2851439e7047
Author: Ben Pfaff <address@hidden>
Date:   Thu Jan 15 20:39:18 2009 -0800

    t-test: Move 'mode' variable from file scope into cmd_t_test().

commit 0edc2d890b40b2941a5c7fe295841127c086dd3a
Author: Ben Pfaff <address@hidden>
Date:   Thu Jan 15 20:37:32 2009 -0800

    t-test: Move 'cmd' variable from file scope into cmd_t_test().
    
    This variable was only used inside cmd_t_test() anyhow.

commit 4fa398a44ed48eaaf84651034c78d22dc5893a0f
Author: Ben Pfaff <address@hidden>
Date:   Thu Jan 15 20:34:43 2009 -0800

    t-test: Remove write-only variable.

-----------------------------------------------------------------------


hooks/post-receive
--
GNU PSPP