I'm for keeping them in CamelCase too. But I still don't like the word
"Open" for ">" as it's still too close to the name "open". There is no
matching "Close" in "<" so why not change "Open" to "UnBox" to match the
name "Box"?
Putting the names into a locale other than "z" is better but still
doesn't resolve the duplicate names problem because "z" will still be in
the path.
I haven't reviewed the other names in PRIMITIVES but I'm still concerned
that there could be others that are really close or the same as existing
names.
Oleg Kobchenko wrote:
--- Don Guinn <[EMAIL PROTECTED]> wrote:
Loading primitiv.ijs clobbers the name "open" in the z locale.
When the names are defined in the z locale CamelCase is converted to
lower case as described in Note at the beginning of the script. This
results in the CamelCase name "Open" for ">" to be converted to "open"
wiping out the "open_z_" verb. The remarks says that all one needs to do
is remove the "tolower" in line 247 of the script, but that doesn't
address the problem of the name conflict for the name "open".
Should the name for ">" be changed to something else? And how many other
conflicts are generated by not keeping CamelCase? Or should we only deal
with CamelCase for the primitive names?
open_z_
+-------+
|open_j_|
+-------+
load 'c:\program files\j\j601\system\packages\misc\primitiv.ijs'
open_z_
+-+
|>|
+-+
Keeping them mixed case is a good idea for separation from
proper definitions.
Another consideration for better separation, is to load
them in a separate locale, e.g. 'jprimitiv', and then
just coinserting into necessary locales.
In general, coinserting separate locales is better than
amalgamating several, esp. disparate, code units
into one locale.
____________________________________________________________________________________
8:00? 8:25? 8:40? Find a flick in no time
with the Yahoo! Search movie showtime shortcut.
http://tools.search.yahoo.com/shortcuts/#news
----------------------------------------------------------------------
For information about J forums see http://www.jsoftware.com/forums.htm
----------------------------------------------------------------------
For information about J forums see http://www.jsoftware.com/forums.htm
