Debiller 777 wrote
> You know, literals are quite useful in case when you want to shorten some
> object initialization. For example #() and {} for arrays and $[]for byte
> arrays. However, if there is a way to add custom literals, for example for
> sets (something like #{} I guess)? how to do it? and can some special kind
> of objects for creating literals easily be added to Pharo?
The discussion on this topic has been quite interesting. However, I want to
circle back to this original question; I think we've wandered from it in
some respects.
The original motivation was "when you want to shorten some object
initialization". Typically, this kind of driver is a performance issue. As
in, "I want to be able to initialize my instances with minimal overhead" so
that e.g. the cost of creating instances is minimized and I can create and
discard instances easily and frequently.
I'm not saying that is the only motivation, but it is largely what I will
address here.
A number of messages discussed somewhat more elaborate syntax for literals,
such as the example for a date #{'2018-05-01') or something close to that.
And someone else will surely want #{'14:30'} for much the same
justification. And yet others will want something else altogether. My of my
all-time favourite design rules was something I read in 1989, loosely called
the 0, 1, infinity rule. As soon as we go beyond one of something, there are
an arbitrary number of possibilities we must deal with. That's not a burden
we want to put on the compiler (or more likely on the parser).
We could imagine that the syntax is a little more elaborate, such as #{Date
'2018-05-01'} in which case the parser could automatically send the
#fromString: message to the receiver Date using the argument of the string.
Such an approach would give a general solution to a simple subset of the
possible initializers one might encounter.
However, it wouldn't handle other kinds of initialization, such as the
Dictionary example I mentioned in my earlier response. It also wouldn't
handle the issue of the implementation of #fromString: being changed and
failing to recompile the literal that was generated independently of it. For
the sake of argument, I think we can reasonably assert that #fromString:
would be assumed to be correct and any changes in its implementation would
not impact the literal that was previously and correctly created from that
literal string.
So, we have a proposal that with a small increase in the syntactic burden of
the language does address a reasonable subset of the originally stated
problem. But, it doesn't solve the general problem. For that reason alone, I
don't agree with increasing the syntax of the language for it.
Another respondent mentioned pool variables. These have the benefit that the
name can be entirely informative and their values can be recomputed any time
one wishes. In fact, they may already be the correct and complete answer.
They aren't without their own costs, of course. Obviously, they must be
defined before they can be referenced in the code that uses them. This
pretty much requires a multiple package approach, requiring one package to
define the pool variables (perhaps with only a place-holder value) and
another package with the code that needs them.
(VA Smalltalk has a technique that allows them to be defined in the same
package, but at a terrible price: their definitions are opaque to the
standard Smalltalk tools. We can discuss this on a separate thread if anyone
wants to know more about that.)
There is also the "once" block that I mentioned elsewhere. It typically uses
a dictionary to cache the result of the first evaluation and then provide
the look up on subsequent evaluations. One could also add a cached result
instance variable to Block and avoid such a look up. It's still not as fast
as a pool variable, of course.
As a side note, I would like to remind everyone about Kent Beck's comments
on literals. I'm paraphrasing him, but essentially there are only a very few
literals which should be allowed to run around naked. The may be 0, 1, '',
and possibly -1. Certainly every other literal should be encapsulated in an
intention revealing name. Does May 1st mean something? If one is going to
use it as I did in the examples above, it had better be given a name that
everyone will be able to understand. For example, any reader would
understand Float pi and the distinction between it and Double pi. A string
of random digits takes considerably more parsing on the part of the reader
to understand its intent.
Lastly, I would encourage the original poster to elaborate on what problem
or problems he is really trying to solve. (Over the years, I ave encountered
many users who request a feature to solve a problem that isn't the real
problem they need to solve. Programmers, too, make the same mistake.)
--
Sent from: http://forum.world.st/Pharo-Smalltalk-Users-f1310670.html
