[Monetdb-developers] [Monetdb-checkins] MonetDB5/src/modules/mal/Tests remote00.mal, , 1.3, 1.4 remote00.stable.out, , 1.4, 1.5

Fabian Fabian.Groffen at cwi.nl
Tue Jul 10 22:04:39 CEST 2007


On 10-07-2007 21:48:03 +0200, Martin Kersten wrote:
>>> It is not optimal, but avoid string construction/analysis
>> Any good reason for that?
>> (you only use it in mdb's list IMHO, where the "cost" is not important,
> cost = also consistent use.
>
> mod and fcn are stored in the global namespace, which makes it possible to
> compare quickly. Otherwise, you have to break "m.f" into two pieces and
> perform expensive string matching in the namespace on both.

consistency is good, however, I fail to see the consistency here.  I use
io.print, but when I reference it I have to use "io", "print"???

> It is used in inspect.get*(), profiler.*(), manual.*(), most
> optimizers (). All cases, as far as I recall, are aligned on this policy.
>
>> and the functionality would be very nice, I use it in remote.get where
>> it is highly undesirable to have two arguments instead of one)
> why? MAL is designed to work with multiple results and arguments.





More information about the developers-list mailing list