Scheme language standardization process
Actually, there is no problem in that:Hi!
2014-03-19 7:06 GMT+01:00 Denis Trapeznikoff <denin@x>:
> Mon, 17 Mar 2014 23:02:52 +0100 от Panicz Maciej Godek
> <godek.maciek@x>:
>
> > I think that there's a nice tradition among the Scheme programmers to
> > use the name "compose" to refer to a composition function. It is much
> > more descriptive than "dollar-asterisk" ("multiply dollars"? "a
> > millionare marries a star"? "jackpot"?), and hence more
> > reader-friendly, and unless you are doing some domain-specific
> > research, your programs usually won't get much longer because of that.
>
> Yes (and I did so, too, at start), but `compose' is too long a word (compare
> it to Haskell's `.').
Haskell is a very nice language, but -- compared to Scheme -- it
conveys a lot of information in its complex syntax. Correct me if I'm
wrong, but I don't think that it would allow you to define the "."
operator if it wasn't already in the language.
((append) is not needed here.)Interestingly, when I was exploring Scheme for the first time, I have
also been introducing such operators as
(define ($_ f . x)
(lambda y (apply f (append x y))))
(define (_$ f . y)
(lambda x (apply f (append x y))))
Sorry, I don't have production examples right before my eyes now, so anything I come up with would be somewhat artificial.It's not only that -- it is also relevant how arguments are applied to
the predicate. To be honest, I have no intuition of whether such
generalization is good. Can you come up with any real-world usage
example? (Like: multiple argument map allows you to easily define the
code that computes the dot product)
Pozdrawiam
M.
_______________________________________________ Scheme-reports mailing list Scheme-reports@x http://lists.scheme-reports.org/cgi-bin/mailman/listinfo/scheme-reports