Yes, that's true, AJOIN is faster. There's definitely room for optimalization.
Maarten
@Rebolek - thanks!
Maarten
I am in need of some docs for R3 - how dows the module system work, mostly... I need exhustive documentation in terms of options, i.e. can I upgrade modules, sign them, etc.? What's possible?
Pekr
Module system was imo never properly finished and/or documented. Dunno if first implementation was done by Carl or BrianH, but Carl asked BrianH to rewrite it. He did so. But I also remember, that he still wanted some PROTECT function changes, etc., which were imo not done. IIRC, Rebolek tried to use the module system, not sure about his experience, but some ppl found the module system quite complicated ....
David den Haring said that they are integrating OpenGL into Rebol3 natively. That sounds exciting!
I can imagine an amazing OpenGL dialect.
Maarten
Quick question: what are the possblie actor types for a networking scheme? Can you define an actor subtype yourself. As an example, we seem to have lost the list function on network ports.
Maarten, here are my notes regarding port/scheme actors:
(Warning, slightly long.)
"Port actions":
create [port] delete [port] open [port /new /read /write /seek /allow] close [port] read [port /part length /seek index /string /lines] write [port data /part length /seek index /append /allow access /lines] open? [port] query [port /mode field] modify [target field value] update [port] rename [port to]
Port actions can be used not only with port!s, but also with port specs (everything make port! accepts: url! block! object! word!) In this case, `make port!` will be called with the spec first, and then the corresponding actor is called with the freshly created port!.
"Series actions":
append at back change clear copy find empty? head head? index? insert length? next past? pick poke remove select skip tail tail? take
I think I also put that, or a slight variation of it, on the rebol.net Wiki once. Unfortunately that's still offline.