[Date Prev][Date Next][Thread Prev][Thread Next]
- Subject: Re: [ANN] Microlight (was Re: paving cowpaths with libraries)
- From: Dirk Laurie <dirk.laurie@...>
- Date: Tue, 21 Feb 2012 08:27:36 +0200
There is absolutely nothing that forces one to say `require"ml".import()`.
Speaking of guilt-by-naming, I was wondering if the class stuff ought
to have explicitly-ml naming, like mlclass(). Other people have sucked
up the words "object" and "class" in their systems; I think
emphasizing ml.mlclass is just *an* object system rather than *the*
object system would ease adoption. It's not like you're going to be
typing mlclass() a lot....
In a long program, one should say `ml=require"ml"` and import (or
assign to a local) only what you use really often. The extra period gives
greater emphasis than a prefix and should not tire out the programmer
too much. It's not like you're going to be typing ml.class() a lot....