My 'bad habit' costs me some hours, but I'm used to use blanks for better
reading my source code. My message was not a question to change IBO, but to
give this information to all which maybe had similar 'problems'.

Ulrich


"Helen Borrie" <helebor@...> schrieb im Newsbeitrag
news:5.1.0.14.2.20020930173805.054d93f0@......

> At 09:29 AM 30-09-02 +0200, you wrote:
> >Hello Ibo users.
> >
> >D5/IBO 4.2Hj
> >
> >I found out that in some TIB_Query TStringList properties blanks are
> >allowed, and in some not. I've not tested all off them, but for example

in

> >the 'FieldsVisible' blanks are not allowed, but in 'KeyLinks' they are
> >allowed.
> >
> >'Not allowed' means : There is no error message, but the expression will

not

> >be parsed correctly.
>
> Stick to the **rule** of NEVER including blanks.
>
> Recently Jason modified the parser behaviour in some cases to strip out

any

> blanks in the x=y strings but it doesn't apply in all cases (parsing
> variations between lone strings like KeyLinks and linked lists like
> Fieldsxx properties).
>
> The blanks are *not* supposed to be "optionally allowed". My own view is
> that mods to "help" sloppy programmers generally cause more problems than
> they solve.
>
> Helen
>
>
>
>

___________________________________________________________________________

> IB Objects - direct, complete, custom connectivity to Firebird or

InterBase

> without the need for BDE, ODBC or any other layer.
>

___________________________________________________________________________

> http://www.ibobjects.com - your IBO community resource for Tech Info

papers,

> keyword-searchable FAQ, community code contributions and more !
>
> Your use of Yahoo! Groups is subject to http://docs.yahoo.com/info/terms/
>
>
>