Fabian wrote:
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"??? "io.print" is an (incomplete) language construct, which is different from arguments telling you to look in the module "io" for the information on element "print".
"io.print(v:any):void" is the real construct you are after
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.
------------------------------------------------------------------------- This SF.net email is sponsored by DB2 Express Download DB2 Express C - the FREE version of DB2 express and take control of your XML. No limits. Just data. Click to get it now. http://sourceforge.net/powerbar/db2/ _______________________________________________ Monetdb-developers mailing list Monetdb-developers@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/monetdb-developers