Hi Gabriele, Gabriele wrote: ==========
> GC> 2. The Call/output doesn't seem to create and fill the > GC> expected file with the results outputted when used - an empty > GC> file is created > GC> and nothing else. > > CALL/OUTPUT actually works correctly on Windows. You can also > redirect the output to a string, like: > > >> call/output "ping localhost" s: "" > == 0 > >> print s > Thanks for demonstrating this way of doing things. I will be VERY useful to many of us I think. > > GC> call/output "E:\Installation de logiciel\REBOL\View 1.3 - > GC> Betas testing\rebview1224031.exe -s xcode.r" %results.txt > GC> print read > GC> %results.txt > > REBOL does not send output to STDOUT on Windows, so CALL/OUTPUT on > REBOL itself isn't useful. > AH! AH! This is the real reason I presume. Seems I misconceived the way it would work as I skipped the fact that the CALL would redirect all the outputted output even the results coming from the newly called copy of REBOL. I could have done better but sometimes evidence is in front of our face without our eyes seeing it. An old "déjà vu" pattern that still survives... many many years! Thanks for this one. Now at least I know that I was looking for is not feasible in the way hoped to do so.I > GC> As it currently stands I don't see the real usefulness of > GC> having a script like easy-vid.r or any other script that would > GC> lauch > GC> another REBOL script during some CLICK and PLAY demo app > GC> - as I planned it initially... > > To launch another REBOL script there's LAUNCH. > Thanks. I'll throw an eye on it too. May be it could have been shorter than learning to use the CALL mechanism. But as I don't know the details I will not speculate here. I'll first go and learn more. Regards, Gerard -- To unsubscribe from this list, just send an email to [EMAIL PROTECTED] with unsubscribe as the subject.
