2014-07-10 18:34 GMT+02:00 Plínio Balduino pbaldu...@gmail.com:
IMO, ! is used when change any global state. A side effect like print on
screen is not enough to cause a ! in the name. I think that's why the
functions print/println don't have ! =)
Than I did it in the 'right' way. In the
2014-07-10 18:46 GMT+02:00 Stefan Kamphausen ska2...@gmail.com:
On Thursday, July 10, 2014 5:28:26 PM UTC+2, Cecil Westerhof wrote:
When a function returns a true/false value you should end it with a '?'.
Clojure Programming says that with side effects you should end the
function name with
Hi,
On Friday, July 11, 2014 11:10:53 AM UTC+2, Cecil Westerhof wrote:
2014-07-10 18:34 GMT+02:00 Plínio Balduino pbal...@gmail.com
javascript::
IMO, ! is used when change any global state. A side effect like print on
screen is not enough to cause a ! in the name. I think that's why the
2014-07-10 19:10 GMT+02:00 Softaddicts lprefonta...@softaddicts.ca:
The fn that does the display is the one having side effects.
Now if your look fn creates the side effect, it should reflect that in its
name.
Look discribes the current location. So it has a side-effect, but as I
understood
2014-07-11 11:28 GMT+02:00 Stefan Kamphausen ska2...@gmail.com:
On Friday, July 11, 2014 11:10:53 AM UTC+2, Cecil Westerhof wrote:
2014-07-10 18:34 GMT+02:00 Plínio Balduino pbal...@gmail.com:
IMO, ! is used when change any global state. A side effect like print on
screen is not enough to
I look at side effects this way, will it ever record some state change that
some
code in the universe will eventually rely on ?
If no, then there's no state change/side effect to care about.
Sending a message is a side effect (a pgm will eventually use it), writing to
a database, ... qualify.
Hi,
On Friday, July 11, 2014 11:33:34 AM UTC+2, Cecil Westerhof wrote:
2014-07-10 19:10 GMT+02:00 Softaddicts lprefo...@softaddicts.ca
javascript::
but as I understood from others it is not about side-effects, but global
state.
as James and I already pointed out, that is not what it
2014-07-11 14:19 GMT+02:00 Softaddicts lprefonta...@softaddicts.ca:
I look at side effects this way, will it ever record some state change
that some
code in the universe will eventually rely on ?
If no, then there's no state change/side effect to care about.
Sending a message is a side
2014-07-11 14:28 GMT+02:00 Stefan Kamphausen ska2...@gmail.com:
On Friday, July 11, 2014 11:33:34 AM UTC+2, Cecil Westerhof wrote:
2014-07-10 19:10 GMT+02:00 Softaddicts lprefo...@softaddicts.ca:
but as I understood from others it is not about side-effects, but global
state.
as James
You do not reuse log file output to propagate state changes.
If you do I would like to know for what purpose...
In my world the ultimate goal of log file output is human consumption with or
without aggregation or alert filtering.
It has nothing to do with your system internal state. It's merely
IMO, ! is used when change any global state. A side effect like print on
screen is not enough to cause a ! in the name. I think that's why the
functions print/println don't have ! =)
Plínio
On Thu, Jul 10, 2014 at 12:28 PM, Cecil Westerhof cldwester...@gmail.com
wrote:
When a function returns
On Thursday, July 10, 2014 5:28:26 PM UTC+2, Cecil Westerhof wrote:
When a function returns a true/false value you should end it with a '?'.
Clojure Programming says that with side effects you should end the
function name with a '!'.
Use the bang! only for things not safe in an STM
In clojure.core, an ending ! indicates a function that is unsafe for STM,
rather than one with side effects. For instance, alter and send are
functions with side effects, but have no ending ! because they're safe to
use in a dosync block.
In other words, an ending ! indicates a function has side
The fn that does the display is the one having side effects.
Now if your look fn creates the side effect, it should reflect that in its name.
But... I wonder why it does so. Looking at something does not change state.
You may be better splitting the side effect away from it or change the name.
14 matches
Mail list logo
