#85: References to variables
-------------------------+--------------------------------------------------
Reporter: toots | Owner: admin
Type: Feature | Status: closed
Priority: 5 | Milestone:
Component: Liquidsoap | Version:
Resolution: invalid | Keywords:
-------------------------+--------------------------------------------------
Comment (by mrpingouin):
I'm glad that this ticket is closed, but I wanted to comment a bit.. I
agree with extending the language, but I can't hurry on that task right
now. When I read about references to sources, I had your second thought:
this is dangerous -- because changing from one source to another without
following the expected protocol would break everything.
On the other hand, if we have references, it would seem strange to forbid
references on sources. So here is the third thought: there is no risk at
all, because we have a good language, one which distinguishes between
things and references to things! An operator taking a source can trust
that this source will never change. Only an operator taking a source
reference would have trouble -- hence, such a thing will probably not
appear soon.
Long life to functional programming (or at least persistant style)!
--
Ticket URL: <http://savonet.rastageeks.org/ticket/85#comment:2>
Savonet <http://savonet.rastageeks.org/>
Let's program our stream !
