>Perhaps we should resurrect the debate about this whole issue on the
>xTalk list, then. It doesn't seem to me that adding yet another chunk
>type is a good way to solve this. No sooner than you add one than
>someone would need two. As I recall, the debate of this issue on the
>xTalk list kind of petered out some time after a proposal for
>something like:
>
>put item 2 delimiter ":" of the long time into minutes
> or
>put item 1 by "/" of directory into rootdir
> or
>put item(":") 2 of the long time into minutes
> Regards,
> Scott
Currently I use:
put line 1 of changedelmiter (Var,";",return) into Var
best would be:
put item 1 delimiter ";" of Var into Var
put item 1 del ";" of Var into Var
as long as these indications are optional.
But:
What about to have the "set itemdelimiter to x" to be local instead of
global
or to have
set globalitemdelimiter to x
and
set itemdelimiter to x --which is then local
local delimiter:
when you use and reuse a number of small handler for for example parsing of
text or complexe data format structured with different delimiters, you get
into trouble with the global itemdelimiter.
In HC you can even see in the debugger-window which is the current
delimiter.
A carefull programmer has therefore to script:
function xsa
put the itemdelimiter into var
set the itemdelimiter to numtochar(30)
.........
set the itemdelimiter to var
return ....
end xsa
the same could be said sith "set the numberformat to 00.0" which is global
and causing similar problems bad results, since calclation may be wrong.
regards
jean-jacques Wagner
