On Fri, May 30, 2014 at 11:54 AM, <svn_grass@osgeo.org> wrote:
- if (strcmp(delim_opt->answer, "\\t") == 0)
- *delim = G_store("\t");
About r60612 and r60613, they are great. But I just noted a changed
interface for some of the modules because they supported also `\t` for tab
besides `tab`.
if (strcmp(delim_opt->answer, "\\t") == 0)
*delim = G_store("\t");
Either parser should support this or this should go to the change of the
interface in 7 wiki page.
When we are on it what about \n, do we want this or not. I would say that
both \t and \n might be helpful but \n can be dangerous sometimes.
Hi, G_option_to_separator supports tab, \t, and newline. Do we need \n? I don’t think so because we can use newline. Maybe delete \t for consistency and use tab only?
···
On Fri, May 30, 2014 at 11:54 AM, <svn_grass@osgeo.org> wrote:
- if (strcmp(delim_opt->answer, “\t”) == 0)
- *delim = G_store(“\t”);
About r60612 and r60613, they are great. But I just noted a changed interface for some of the modules because they supported also \t for tab besides tab.
if (strcmp(delim_opt->answer, “\t”) == 0)
*delim = G_store(“\t”);
Either parser should support this or this should go to the change of the interface in 7 wiki page.
When we are on it what about \n, do we want this or not. I would say that both \t and \n might be helpful but \n can be dangerous sometimes.