[EMAIL PROTECTED] wrote:
> Hi,
>
> Can you give a small example of the problem? Nothing like that has shown up
> in our testing, so it may be something in the way you are using it that we
> are unaware of. Thanks.
Hi Jim, :-)
as for script I sent to the list yesterday, it still crashes even under new 2.2
release. What's happening during dir?
>> source dir?
dir?: func [
"Returns TRUE if a file or URL is a directory." [catch]
target [file! url!]
/local info
][
info: throw-on-error [info? target]
either none? info [false] [info/type = 'directory]
]
>> source throw-on-error
throw-on-error: func [blk][
if error? blk: try blk [throw blk]
:blk
]
>> source info?
info?: func [
"Returns information about a file or url." [catch]
target [file! url!]
][
throw-on-error [
target: make port! target
query target
]
either none? target/status [
none
] [
make object! [
size: target/size date: target/date type: target/status
]
]
]
>> source query
query: native [
"Returns information about a file or URL."
port [file! url! block! port!]
]
>>
Are objects created that way destroyed properly?
I also tried to set recycly/on in the beginning of the script, but it was of no
help to me ...
Thanks,
-pekr-
>
>
> - jim
>
> At 12:55 PM 11/3/99 +0100, you wrote:
> >I have massive problems with the new verion.
> >
> >read-io from a opened tcp port behaves totally different from the previous
> >versions.
> >
> >It puts the third parameter (length or maximum number of bytes to read)
> >before the received messages into the buffer and does not get all the bytes I
> >expect in the message.
> >Only 11 are in the buffer after reading.
> >
> >Anyone encountering a similar behaviour ?
> >
> >AR
> >
> >--
> >Sent through Global Message Exchange - http://www.gmx.net
