World: r3wp

Well, I used the encryption key as a string instead and encrypted 
to 256 bits using Rijndael and successfully decrypted with Rebol. 
 But aescrypt was not able to decrypt the file :(

I had padding set to false

If you have counters block and want to increment it, is there some 
better solution than this one?
	b: ["a" 1 "b" 1]
	change f: find/tail b "a" f/1 + 1
	probe b

don't know if any of these are better(and in which sense better):

change n: next find b "b" n/1 + 1

b/("a"): b/("a")  + 1
...

This does it without using a temporary word....and it should work 
even if the counter name is not amenable to Cyphre's path notation 
(ie you are using something more exotic that strings for counter 
ids, or are using an older version of /Core).
   b:  next find/skip head b "a" 2 b b/1: b/1 + 1
Just remember to reset ....
   b: head b
....once in a while:)

b/("a"): b/("a")  + 1
is the winner as it's a little bit faster and shorter.

Isn't this a bug?

>> make-dir %tmp/
== %tmp/
>> write %tmp/test ""
>> exists? probe first reduce [join %.\tmp "\test"]
%./tmp\test
== true
>> delete probe first reduce [join %.\tmp "\test"]
%./tmp\test
** Access Error: Cannot delete ./tmp\test
** Near: delete probe first reduce [join %./tmp "\test"]
>> delete probe first [%.\tmp\test] ;this works
%./tmp/test

I expect that when it's possible to get true on exists?, the delete 
should work.

I get false on the exists? line (linux, 2.7.6)

Oldes, what filesystem ?

EXISTS? creates a port from the file! argument, then queries that.
DELETE doesn't work with ports.

I guess it is the creation of a port or QUERY which is able to handle 
backslashes, and DELETE cannot.

I think you should normalise your files using TO-REBOL-FILE.

ntfs. And yes, I normalise now, just wanted to know, why it's different 
and if it's correct. (because I've spent some time to figure out 
this exists?/delete difference).

in other words.. I was expecting, that when I join something to rebol 
file, it will normalise it for me.

But maybe it's more related how join behaves:
>> join %test as-binary "test"
== %testtest
>> join %test ["test"]
== %testtest
>> join %test [as-binary "test"]
== %test#%7B74657374%7D
>> rejoin [%test as-binary "test"]
== %test#%7B74657374%7D
but you ar right, it's my fault that I was lazy.

There is another way to put a directory together with a file than 
'join, and it handles more cases with the forward/back-slash on its 
own:
>> Dir: %foo/bar
== %foo/bar
>> File: %test  
== %test
>> Dir/:File    
== %foo/bar/test
>> Dir: %foo/bar/
== %foo/bar/
>> Dir/:File     
== %foo/bar/test
>> File: %\test  
== %/test
>> Dir/:File   
== %foo/bar/test

I know, but that does not solve my case where I had to build path 
from external sources, which could contain the backslash. Like:
>> dir: %test/
== %test/
>> file: ".\LIBRARY\something"
== ".\LIBRARY\something"
>> dir/:file
== %test/.\LIBRARY\something

But to-rebol-file makes it valid for sure:
>> to-rebol-file dir/:file
== %test/./LIBRARY/something

To read the content of a shared folder on a machine, it's :
	read %/machinename/sharename/


But how (if its possible) can I read the list of the shared folders 
?

	read %/machine/		...does not work !!

I believe the share has to be a mapped drive to show up that way. 
I don't recall every enumerating shares this way, but maybe someone 
else has.

I think I remember seeing something of the sort with:
read%//

But I'm not on Windows right now, so I can't check

Do you think that this is correct?
>> integer? round 232.2
== true
I was somehow expecting that the number is still decimal = 232.0

Ah.. now I see that R3 works as I expect.

ROUND under R2 was a mezzanine, and was designed so the result would 
be an integer when possible, for use as a loop counter. It's no longer 
a mezzanine under R3. I don't remember if it was mentioned that it 
was an intentional change.

And we don't need to use integers for loop counters anymore.

we can use real numbers?

In R3, yes. There is an implicit to-integer.

Is it possible to change file-modes of directory? This doe not work:
>> get-modes %/f/dir/ 'creation-date
== 26-Oct-2010/16:55:30+1:00
>> set-modes %/f/dir/ compose [creation-date: (now)]
** Access Error: Cannot open /f/dir/
** Near: set-modes %/f/dir/ compose [creation-date: (now)]

What is the best way to form decimal and avoid the E notation?
>> form .02
== "2E-2"

form-decimal ... Gabriele has a version around

Nice challenge. To find the smallest mezz to do so

Is there a sql like dialect ( selects ) for rebol blocks in memory 
( not disc based )

I am thinking of coverting a simple read only database to ram based 
for speed ...

I thought I read of one once .. but maybe I am wrong.

I know a good one, it's called PARSE IIRC

so I can just change the scheme from odbc to ram or whatever

EXTRACT works well for that, and maybe MAP-EACH too if you do nested 
blocks.

No joins involved

There are some databases that are RAM-based already and have SQL.

For that matter, RebDB is SQL-like and RAM-based, iirc.

Ah.. I can look at rebdb then

my queries are currently taking 2 seconds and I need subsecond performance

You might look at EXTRACT or MAP-EACH then. For simple queries with 
no joins, SQL is overrated.

If you give us your actual script we can find some improvment rooms. 
Despite beeing lazy, we are not bad at such game.

(if it's not a bloated one)

I'm hacking into FreeDiams .. a free French drug interaction database 
:)

Don't trust French commercials

It's a GPL app to do drug prescribing and drug interactions .. I 
am just using their database

Once the database is in memory you don't necessarily need to do set 
operations (SQL select). You can do iterative operations much more 
quickly.

source is here https://fd.cloud-ehr.net/drugreactions.txt