Got the player moving in the map! And, got the map to be deadly in its own special way.
HeadCrush -> do showMessage "You die." endThread
Even winning the game is implemented. The game has a beginning, a middle, and an end.
I left the player movement mostly unconstrained, today, while I was working on things to do with the end of the game, since that makes it easier to play through and test them. Tomorrow, I will turn on fully constrained movement (an easy change), implement inventory (which is very connected to movement constraints in Scroll), and hope to start on the spell system too.
At this point, Scroll is 622 lines of code, including content. Of which, I notice, fully 119 are types and type classes.
Only 4 days left! Eep! I'm very glad that scroll's central antagonist is already written. I don't plan to add other creatures, which will save some time.
Last night as I was drifting off to sleep, it came to me a way to implement my own threading system for my roguelike. Since time in a roguelike happens in discrete ticks, as the player takes each action, normal OS threads are not suitable. And in my case, I'm doing everything in pure code anyway and certianly cannot fork off a thread for some background job.
But, since I'm using continuation passing style, I can just write
fork, that takes two continuations and combines them,
causing both to be run on each tick, and recursing to handle combining
the resulting continuations.
It was really quite simple to implement. Typechecked on the first try even!
fork :: M NextStep -> M NextStep -> M NextStep fork job rest = do jn <- job rn <- rest runthread jn rn where runthread (NextStep _ (Just contjob)) (NextStep v (Just contr)) = return $ NextStep v $ Just $ \i -> do jn <- contjob i rn <- contr i runthread jn rn runthread (NextStep _ Nothing) (NextStep v (Just contr)) = return $ NextStep v (Just contr) runthread _ (NextStep v Nothing) = return $ NextStep v Nothing endThread :: M NextStep endThread = nextStep Nothing background :: M NextStep -> M NextStep background job = fork job continue demo :: M NextStep demo = do showMessage "foo" background $ next $ const $ clearMessage >> endThread
That has some warts, but it's good enough for my purposes, and pretty awesome for a threading system in 66 LOC.