Hi Gerard,
On Sunday, January 11, 2004, 10:48:35 PM, you 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
Esecuzione di Ping GABRIELE [::1] con 32 byte di dati:
Risposta da ::1: durata<1ms
Risposta da ::1: durata<1ms
Risposta da ::1: durata<1ms
Risposta da ::1: durata<1ms
Statistiche Ping per ::1:
Pacchetti: Trasmessi = 4, Ricevuti = 4, Persi = 0 (0% persi),
Tempo approssimativo percorsi andata/ritorno in millisecondi:
Minimo = 0ms, Massimo = 0ms, Medio = 0ms
>>
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.
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.
Regards,
Gabriele.
--
Gabriele Santilli <[EMAIL PROTECTED]> -- REBOL Programmer
Amiga Group Italia sez. L'Aquila --- SOON: http://www.rebol.it/
--
To unsubscribe from this list, just send an email to
[EMAIL PROTECTED] with unsubscribe as the subject.
