Thanks for the snippet Nicolas but that is not the problem! I do know
how to implement the 'undo' functionality...In OOP this is called the
"Command" design pattern...The command interface has execute(from, to)
and undo(from,to) (which calls execute with reversed arguments)...That
part is not h
>
> 1. Gary Bernhardt has been playing with a "new" approach he calls
> "Functional Core, Imperative Shell". Essentially, it's another take on
> the question of how to limit the scope of mutation in order to get the
> most out of the correctness of mutation-free algorithms and the
> performance of
On 26/08/12 09:51, Patryk Bukowinski wrote:
Hi Jim,
Reading your story I've got an impression that you make 'functional'
and 'immutable' a synonym, not default.
Implementation should be more transparent.
In APL func&vect programming languages fammily there are tools which
amends values in pl
Hi Jim,
Reading your story I've got an impression that you make 'functional' and
'immutable' a synonym, not default.
Implementation should be more transparent.
In APL func&vect programming languages fammily there are tools which amends
values in place.
It feels so natural, part of a language used
On Sun, Aug 26, 2012 at 11:16:29AM +0100, Jim - FooBar(); wrote:
> On 26/08/12 11:03, Joshua Ballanco wrote:
> >I would love to have some time to look into the details of your specific
> >problem more, but in the absence of time, might I suggest two quick
> >points:
>
> Well, feel free to have a l
On 26/08/12 11:03, Joshua Ballanco wrote:
I would love to have some time to look into the details of your specific
problem more, but in the absence of time, might I suggest two quick
points:
Well, feel free to have a look at the project on github when you find
some time ( https://github.com/ji
On Sat, Aug 25, 2012 at 09:01:21PM +0100, Jim - FooBar(); wrote:
> Hello everyone,
>
> in this post I'm not asking for something specific, but rather I'd
> like to spark a discussion regarding the issue of performance
> within the functional paradigm...most of the things i will mention
> will pro
+1
i stay functional if possible and fall back to mutable on isolated,
performance critical spots if i can't get it done fast enough in a
purely functional way.
i solved the move-mess-up-everything problem by forcing a move to
implement both apply and unapply on a game board. (it was a java
proje
Hello everyone,
in this post I'm not asking for something specific, but rather I'd like
to spark a discussion regarding the issue of performance within the
functional paradigm...most of the things i will mention will probably
not be news for most of you...Hopefully, however the issues I plan
