Re: Syntax|Parse error on code that used to run

[richard]

On Fri, Mar 28, 2014 at 04:20:43PM -0400, Mike Miller wrote:
> On Fri, Mar 28, 2014 at 1:34 PM, richard wrote:
> > Out of curiousity, why do you think the change is an improvement?
> 
> IMHO more whitespace makes code more readable and less ambiguous.
> 
> Especially if that quote were a single-quote, is it a transpose
> operator on x or the start of a string? Spaces separating tokens makes
> for more readable and understandable code. Especially with the amount
> of punctuation in your code sample.
> 
> Also why was a space required *before* the variable and a preceding
> quoted string, but not after? Now it's consistent.
> 
> Those are the main reasons it looks like an improvement to me.
> 
I am all for readability and simplicity. That code is the result of trial 
and error near a leading edge of development - the space is there because 
Octave says it must be there, and for no other reason. Similarly, the 
punctuation is there because postgres says certain things must be where 
they are and Octave requires more punctuation to get those things where they 
need to be. . . 

The string actually presented to the postgres server (old i.e. 3.6 version) 
would have looked something like this: 
  values (' Augustus', 0.01, 0.02, .....etc ); 
and now looks like this (3.8.1 version) : 
  values (' Augustus ', 0.01, 0.02, .....etc );

I'm happy with whatever works. Did I mention my thanks to all working 
to develp Octave? 

As to why I prefer to hold my data in a database, I'm happy to confess 
that the choice is probably subjective. 

Richard