[GRASS-dev] erratic behavior of v.in.ascii with WinGRASS

[Hamish]

> Michael:
> > As an aside, the | character seems like an odd default separator
> > for data fields in GRASS. I suppose it's a holdover from the
> > ancient past. But the fact that this is also has meaning as a pipe
> > seems to make it a risky separator in general. What about switching
> > this to something else in GRASS 7?

Glynn: 
> There's only thing that's "risky" about using "|" is that certain
> bugs in code which executes commands will show up rather than getting
> overlooked.
> 
> If such bugs exist, they should be fixed, rather than having
> individual cases worked around.


just to point out that just about any uncommon character (ie unlikely
to show up in an attribute's text string (& if so needs quoting)) is
likely to be already used by Bash to do something or other.


Hamish



      ____________________________________________________________________________________
Looking for last minute shopping deals?  
Find them fast with Yahoo! Search.  http://tools.search.yahoo.com/newsearch/category.php?category=shopping