What was the Capture() bug?

[Carlo Hogeveen]

Sammy,

The current TSE v4.50.19's read.me file states:
"capture() of a shell command was broken. Fixed."

Because I publish macros, I try to make them backwards compatible with older TSE versions, because not everybody immediately updates their TSE installation to the latest version.

For my current "masterpiece in progress" I am wondering whether I should use the Capture() statement as the more efficient choice, or the Dos() or lDos() statement as the more backwards compatible choice.

So I can make this choice:
1.
In what way was Capture() broken?
2.
Since when was Capture() broken this way?

Carlo

[S.E. Mitchell]

Capture() was broken in v4.50.18.
The bug (introduced when I was trying to decide if I should use
cmd.exe or %COMSPEC% as the Windows shell command) occurs when one
tries to capture output of a known shell command. I foobar'ed the
parameters to the shell: instead of switches cmd.exe, I was passing
switches after cmd.exe.

> --
>
> ---
> You received this message because you are subscribed to the Google Groups "SemWare TSE Pro text editor" group.
> To unsubscribe from this group and stop receiving emails from it, send an email to semware+u...@googlegroups.com.
> To view this discussion visit https://groups.google.com/d/msgid/semware/001201dca7ce%24288d1b30%2479a75190%24%40ecarlo.nl.

[Carlo Hogeveen]

That is good news.
That made the bug exist for the 6 days between TSE v4.50.18 and v4.50.19.
The people who always update TSE are not affected, and the people who update TSE infrequently are unlikely to be affected.
And TSE v4.50.19 is the version that is published on the Semware website.
I now feel at ease using the Capture() statement in published macros.
Thanks,

Carlo

To view this discussion visit https://groups.google.com/d/msgid/semware/CA%2BgEvkYkUghdoV7Q_6qM2v8eiscf-r6%2BryNbo3_3euQyvAtXDw%40mail.gmail.com.