[REBOL] Re: Profiling Rebol API to DyBASE
From: robert:muench:robertmuench at: 22-Dec-2003 9:31
On Mon, 22 Dec 2003 00:32:02 +0300, Konstantin Knizhnik
<[knizhnik--garret--ru]> wrote:
> I made all methods from persistent external functions. So now nstead
> of doing "obj/modify" you should use "modify obj". The name of all
> methods is preserved, except "load" method which is removed to
> "load-persistent" (to avoid conflict with system function).
> I hope that other methods (store, modify, deallocate,...) will not
> cause conflicts. In future if Rebol will provide efficient
> mechanism for methods, I return these methods back to persistent
> class.
Hi, you can avoid name clashes today too. Just put the functions into an
own context.
dybase: context [...]
Than we can use those functions like 'dybase/load and you don't have to
move them back into the persistent context as this will never make any
sense in Rebol. The "problem" we have seen, is not an implementation issue
of Rebol instead it's a design issue of the interface. This will never
change, because this is an intended feature of Rebol.
--
Robert M. Münch
Management & IT Freelancer
Mobile: +49 (177) 245 2802
http://www.robertmuench.de
