On Sat, Apr 6, 2013 at 5:42 PM, Steven Degutis wrote:
> What do you think? What approach would you take in this situation?
I guess I'd turn it around and ask what new problems you think
functional programming introduces for testing - and why do you think
that?
In general, I've found that writing
Forgive me if I completely misunderstood your question. Replies inline.
One way is to use `with-redefs`. This technique would be used at every
> level along the pyramid (except the bottom level which doesn't call
> anything else).
>
>
This would be similar to mocking, correct? If so, what'd be wro
Disclaimer: this isn't strictly about Clojure, more about semi-functional
programming techniques, which Clojure excels at. (Plus I'm using Clojure
for it.)
Lately I've been experimenting with ditching the conventional MVC approach
to writing a web app.
Now controllers are just dead-simple func
I agree. I see nothing that sets the code pointer back to the start of the loop.
I also agree with Michał's suggestion that getting rid of global state
and making this more functional in style will make it much easier to
read, debug and maintain - as it stands it not very idiomatic for
Clojure.
S
PS. The above would mean that the loop/recur terminates as expected,
it's just that next time this function is called it starts executing
instructions at the wrong spot.
Anyway, I agree that factoring the code in a more manageable fashion
may be a more useful first step than hunting individual bug
Not sure why you're using (- end-index 2) in the printed message.
Also, you can use (dec end-index) in your termination condition.
As for the main problem, I haven't studied your program very closely,
but it seems to me that your program counter may never get reset to
the beginning of the loop, in
If there's too much incidental complexity and you know it, try working on
reducing that first. It's quite likely the bug will shake out while you're
doing so, and if not, it is likely to be much easier to find after you
simplify and refactor the code.
--
--
You received this message because you
Hello, I'm a new clojure programmer--but after learning a bit of clojure
including iteration, some core high order functions, and a little bit about
state management I decided to try my hand on a brainfuck interpreter.
Located here:
https://github.com/recursor94/brainfuck.clj/blob/master/brainfu
First post, first mistake, ashamed that I am. Big time. I spoke before I
thought. No need say more here.
On Saturday, April 6, 2013 11:51:26 PM UTC+2, Laurent PETIT wrote:
>
> Hello Jeremy,
>
> 2013/4/6 JeremyS >:
> > Here I am on my very first post here, finding myself adding to a troll
> th
Hello Jeremy,
2013/4/6 JeremyS :
> Here I am on my very first post here, finding myself adding to a troll that
> has gone far beyond what I would have imagine for the clojure google group.
>
> First, to Fogus, your book with Chouser is a the perfect start on the road
> to lisp enlightenment and I
Regardless of your personal feelings about anyone here, bullying and
namecalling directed at mailing list members is off-topic and inappropriate
use of the mailing list. Without naming names, I ask anyone who feels
tempted to engage in such childish behavior on-list to please refrain from
doing so
Here I am on my very first post here, finding myself adding to a troll that
has gone far beyond what I would have imagine for the clojure google group.
First, to Fogus, your book with Chouser is a the perfect start on the road
to lisp enlightenment and I am impatient to discover the second edit
12 matches
Mail list logo
