World: r3wp

if you want to only see those successfully opened, I would put the 
'append  after server: i

do you regard the all [..] ?

won't attempt always return the same value?

I do not follow ?

oh .. I isee it doesn't

how about


attempt [ print i close open join tcp://server: i append opened i 
]

and do without the p, and the all ....

for i 65536 1 [ attempt [ print i close open join tcp://server: i 
append opened i ] ]

for i 1 ...

of course, you can also omit the print

or shorten it to 'prn ...

'prin

Thanks Graham and Sqlab. One step further if you please. What would 
you suggest the steps would be to test the code. Right now when I 
run the test I get no opened ports. I've turned the firewall off 
and on but the results are the same. 

I've been studying the nettools.r code and thinking that maybe I'm 
not thinking this right. What I want to know is if a certain port 
will allow it to be open so that this particular application has 
can use.it. What is happening is customers are installing the app 
and having trouble because these certain ports are unavailable. What 
I wanted to create was a quick and easy pre-install test to verify 
these ports were open. This partly due to the fact that they way 
the software was written it doesn't tell you that a closed port is 
the problem. It simply stops worting. 
I appreciate the feedback you have given.

Cheyenne has such opened listen port detection capabilities (added 
recently), you can extract the code from the SVN repo (search for 
'list-listen-ports function) : http://code.google.com/p/cheyenne-server/source/browse/trunk/Cheyenne/misc/win32.r


Linux and OS X versions are also available in %misc/unix.r and %misc/macosx.r

Thanks Doc.

what the code checks for is if anyone is listening at a certain port 
...not whether the firewall is open or closed.

If the firewall is off, but no one is listening ... then you'll get 
a closed port
same as if the firewall is on, and someone is listening...

what about R3 status ? make uptodate  R2 is very fine but i would 
prefer a R3 version with GUI and ODBC or MYSQL ..................;

The R3 GUI is still in development. The database model hasn't even 
been designed yet. You can make wrappers for ODBC and MySQL if you 
want to write the extensions - Robert has already started doing so 
for SQLite. Once device extensions are supported, we can start to 
get to work on the database model.

R3 Status: The beta will come out without GUI, database or (unless 
there is some miracle) SSL.

some miracle

 in this case meaning a community member with the time volunteering 
 to do the work.

do you have a plan for the beta realase ?  one week, month,

It's a little flexible - outside circumstances have affected the 
timing already.

thank you for your effort on

thank you for your effort on R3 and R2

i am just like an end user on R3.  and for me i am not a guru like 
you and others !!!!!

i just want to see more info and screen on the new GUI  of  R3 (i 
am very curious :-) )

There will be no miracle that will bring the GUI or database to the 
first R3 release - they just aren't done yet, and can't be done with 
the level of community involvement that the alpha releases have engendered. 
Too many critical people are waiting for a beta or full release before 
they will even start to get involved. Fortunately we are on the rapid 
release model, so there is no such thing as a "final" or "full" feature 
set, just the feature set of a particular release.

Thanks Graham.

If you are interested in the GUI, get involved. We *really need* 
non-gurus - the GUI is designed for them.

If non-gurus can't use the GUI, it's a design flaw that needs to 
be fixed.

we non gurus need to wait for the gui .. or is it out now??

and this is in the wrong group ...

Reichart hasn't yet restored the right group.

Ok, let's create a new r3 group ...

No, let's not.

Can't wait forever ...

I'm not waiting.

anyone got a code color rinser for R source?

http://www.rebol.org/view-script.r?script=color-code.r

>> a: [1 2]                 
== [1 2]


>> reduce [a swap a next a]

== [[2 1] [2 1]]

Why it doesn't return [[1 2] [2 1]] ?

This works as I expected:
>> a: [1 2] 
== [1 2]
>> compose/deep [[(a)] [(swap a next a)]]

== [[1 2] [2 1]]

Hm, I understand that now:

>> a: [1]

== [1]


>> reduce [a append a [1]]
== [[1 1] [1 1]]

Interesting. I never knew that.

it would be very helpfull if rebol could let you define functs that 
would warn you if you used or defined any global words .. 


I suppose my programs are 100% more uncertain because I forget to 
include some of the words I defined in words as local. If some 'funcstrict' 
for example would warn me of any such mistake I would sleep much 
better. Other but worse option is that there would be some lint like 
tool that would look at code and warn you of these

AFAIK, static code analysis cannot be used on REBOL source code to 
infer the runtime behaviour accurately , word! values can be constructed 
and dynamically bound at runtime. Same reason why REBOL is not compilable.

Regarding capturing of globally defined words in a local context, 
as Gabriele likes to say : "for every code you would write that would 
work for you, I can write an example code that will break it" ;-)

Btw, R3 modules would minimize this issue to the local module only.

yes analysis could be hard or impossible if you look at more unusual 
things you can do.. but at least so that all. 


about second, maybe you mean the same.. but I just want that my certain 
functions set no global words, at least not directly with word: ~expr~ 
or set 'asd set [ asd asd ] ..

setting no global words: use a context

I imagine when you now set some word in some function it looks at 
/local words and it it's there it creates a local word, if not it 
just sets a word (globaly).. let's say that there is funcstrinct 
that in second case just throws an error (probably something like 
that could be made in rebol itself)

Henrik: but I don't want to make each function a context (probably:) 
) .. I have to admit I don't know much about contexts .. only that 
it's like object