Testing on WIN XP with:
c:newlisp>newlisp qa ext
Quote
TESTING FINISHED WITH ERRORS:
>>>> net-receive-udp failed nil
>>>> net-send-udp failed nil
newLISP v.8.1.5 Copyright (c) 2004 Lutz Mueller. All rights reserved.
Whats wrong?
Most likely nothing is wrong, just timing difficulties try to run it again or run the the udp examples in the examples directory manually (they are also in the manual) opening a different command windows for client and server.
It was just difficult to get it right in an automatic fashion, but I have tested all routines on all platforms and they should be fine.
Lutz
On WIN XP in the office it seems to hang in net-accept:
C:newlisp>newlisp qa ext
Testing built-in functions ...
! != $ % &
* + - / <
<< <= = > >=
>> NaN? ^ abs acos
add address and append apply
args array array-list array? asin
assoc atan atan2 atom? begin
beta betai binomial break case
catch ceil change-dir char chop
close collect command-line cond cons
constant context context? copy-file cos
count cpymem crit-chi2 crit-z current-line
date date-value debug dec define
define-macro delete delete-file device difference
directory directory? div dolist dotimes
dotree dump dup empty? encrypt
ends-with env environ error-event error-number
error-text eval eval-string exec exit
exp expand explode fft file-info
file? filter find first flat
float float? floor for format
fv gammai gammaln get-char get-float
get-integer get-string get-url getenv global
if ifft import inc index
integer integer? intersect invert irr
join lambda? last length let
list list? load log lookup
lower-case macro? main-args make-dir map
match max member min mod
mul multiply name net-accept
user reset - in function net-accept
called from user defined function test-net-accept
called from user defined function qa
user reset - in function net-accept
called from user defined function test-net-accept
called from user defined function qa
CTRL-C does not terminate it. It reenter the function.
Manualy entering the lines of test-net-accept seems to work.
If newLISP-tk works on your machine then networking works. Control-C on Win32 in newLISP will not always break out of newLISP but stay in some i/o functions.
About the qa file: it is a quick program for me to test newLISP functionality. When certain routines specially those depending on process fail (or rarely on net-working) , then that does not mean anything until testing those functions manually.
If networking fails I wonder if something is not setup right on that machine? Some functions are difficult to test in an automatic fashion and I will put no more work into qa, then necessary to work on the machines I have access to.
But you are welcome to investigate this case on your machine and make modifications to qa, which I could incorporate in upcoming versions of qa.
Lutz