Unexpected "word" parsing

[Mike Bonner]

Thx richard.  Saw a post by you that mentioned it, I think it'll do what I
need, thanks!  I'm looking for a way to do it on windows too, have been
trying to find out if it can be done with vbscript using setwindowpos() but
haven't found the right info yet.  If it can be done in vbscript, its
likely I can use do <script> as vbscript, or even have an external script
file that I call and pass the window id.  Will keep digging till I figure
it out, and my apologies, I didn't realize I had derailed the "word" topic.
Oops

Pete, yeah I was looking at the right one, just was pointing out the other
2 delimiters that weren't mentioned in the specific line I pulled from the
dictionary. Tab and return were farther down.Chose that line because it
specifically defined "quoted parts" as a word.   Kinda worries me though.
I've written stuff that uses word chunks in a big way, and all my tests
worked dandy.  I'll need to revisit how the data being used and entered and
decide if there is an issue.  I sometimes forget the incredibly wide range
of ways people can choose to enter information. Consistency matters, and
people aren't.


On Sat, Dec 6, 2014 at 10:01 AM, Peter Haworth <pete at lcsql.com> wrote:

> Hi Mike,
> I think you were looking at the dictionary entry for "words" - the
> definition for "word" is where it mentions the return/tab.
>
> Pete
> lcSQL Software <http://www.lcsql.com>
> Home of lcStackBrowser <http://www.lcsql.com/lcstackbrowser.html> and
> SQLiteAdmin <http://www.lcsql.com/sqliteadmin.html>
>
> On Fri, Dec 5, 2014 at 4:24 PM, Mike Bonner <bonnmike at gmail.com> wrote:
>
> > From the 6.6.2 dictionary, though that line doesn't mention tab and
> > return.  Its just not handling quoted parts of a string very well it
> seems.
> >
> >
> > Summary:
> > Used with the sort command, number function, and is among and is not
> among
> > properties to designate space-delimited or quoted parts of a string. Also
> > used with the find command to search for one or more entire words.
> >
> > On Fri, Dec 5, 2014 at 4:23 PM, Bob Sneidar <bobsneidar at iotecdigital.com
> >
> > wrote:
> >
> > > If that is the case, then word 1 return the correct value, word 2 is
> > > incorrect. Word boundaries are spaces and there are no spaces so word 1
> > > *should* be the whole string and word 2 should be empty.
> > >
> > > Bob S
> > >
> > >
> > > On Dec 5, 2014, at 13:42 , dunbarx at aol.com<mailto:dunbarx at aol.com>
> > wrote:
> > >
> > > word 1 of a string like myProps["cProp"] returns the whole string.
> Word 2
> > > returns"cProp"]
> > >
> > > Since cProp is enclosed in double quotes I was expecting:
> > >
> > > word 1 --> myProps[
> > > word 2 --> "cProp"
> > > word 3--> ]
> > >
> > > This is with LC 6.6.2/OSX.
> > >
> > > Pete
> > >
> > > _______________________________________________
> > > 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
> > >
> > _______________________________________________
> > 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
> >
> _______________________________________________
> 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
>