item delimiter defaults

Peter Haworth pete at lcsql.com
Fri Nov 22 00:12:12 CET 2013


Seems like most folks issues revolve around having tab as a delimiter, no
doubt because of the way LC returns data from a database, so if a new
"thingy" named "column" could use the columnDelimiter setting, I could live
without a global or stack level default.

Pete
lcSQL Software <http://www.lcsql.com>


On Thu, Nov 21, 2013 at 2:21 PM, Monte Goulding <monte at sweattechnologies.com
> wrote:

>
> On 22/11/2013, at 9:02 AM, Robert Brenstein <rjb at robelko.com> wrote:
>
> > I second this suggestion. It adds a new feature, so backward
> compatibility is not an issue, and it extends language with something quite
> useful and a better approach that changing global default.
>
> Wouldn't we still need to ensure the columnDelimiter is what we want it to
> be and set it back to what others expect like Jacque was pointing out it's
> pretty annoying. Working with the folder drives me nuts for example...
>
> --
> Monte Goulding
>
> M E R Goulding - software development services
> mergExt - There's an external for that!
>
>
>
>
>
> _______________________________________________
> use-livecode mailing list
> use-livecode at lists.runrev.com
> Please visit this url to subscribe, unsubscribe and manage your
> subscription preferences:
> http://lists.runrev.com/mailman/listinfo/use-livecode
>


More information about the use-livecode mailing list