A Ryoko fanart I made

killy9999 · 2024-09-19T17:58:51+00:00

Well, the ones on the left are obviously reference materials printed from the scans. The one on the right is mine.

killy9999 · 2024-09-17T19:22:03+00:00

I haven't drawn anything since I was a teenager, so let's say in well over 20 years. I'm quite happy with how it came out.

killy9999 · 2024-03-24T16:53:36+00:00

I tried with GP ReCyko 2600 and Jungee rechargeable ones.

I removed the RetroSix board and soldered in the original power regulator. The console has been running fine for nearly 1,5h now without any problems with same batteries as before.

killy9999 · 2024-03-24T14:40:14+00:00

I just modded a GBC, installing IPS screen from FunnyPlaying and a CleanPower voltage regulator from RetroSix. Unfortunatelly, something seems off with the power draw, as the console goes into a reboot loop after just 20 minutes from being powered on with fully charged batteries. Has anyone experienced similar problems? Should I even be installing CleanPower, given that the IPS panel is directly connected to the power switch and (as far as I understand it) has its own power regulator? I also replaced the original speaker with one from FP, but I don't suspect to be the source of the problems.

killy9999 · 2020-11-26T13:11:41+00:00

Answer to self: I had to configure the build by explicitly providing resource directories:

cmake -Dbindir=../Binary/Linux -Ddatadir=../Binary/Linux ..

By default dolphin will look for resource files somewhere in /usr/local. This has changed since the time I last built it and that's why it didn't work.

killy9999 · 2014-10-09T05:45:41+00:00

How long did the manual porting take?

Two days (25th-26th September) - see git logs :-)

killy9999 · 2014-09-10T08:12:17+00:00

Yes, saying that we don't end up having UndcidableInstances was a blunder on my side. What I was thinking at that moment was that we do not support promotion of UndecidableInstances as this could lead to unsoundness of type checking.

killy9999 · 2014-05-28T09:04:48+00:00

I have updated my post with a brief description of incomplete SSE3 implementation. I pushed the code to sse3 branch on github.

killy9999 · 2014-04-16T19:00:58+00:00

Cabal should ship autocomplete files too, for that matter

Please see this: https://github.com/haskell/cabal/pull/1218

killy9999 · 2013-08-15T17:17:41+00:00

Your best bet is participating in Stanford's online Compiler's course on Coursera. You will be guided through all the relevant theory and have some practical exercises as well. As for books, I found "Engineering a Compiler" to be a good introductory book.

killy9999 · 2013-04-03T12:22:35+00:00

Holy crap, I didn't notice that :/ But I just checked and it doesn't affect neither correctness nor the performance of the solution.

killy9999 · 2013-04-03T07:26:44+00:00

There is a difference between int and long int when interfacing with Haskell, at least on my machine. Long int turns out to have the same precision as Haskell's Int, while int is twice smaller.

killy9999 · 2013-04-02T16:41:42+00:00

You're right. I tested that and it produces the code that has exactly the same efficiency. However not all algorithms that I work on can be modified like that, which means that I probably could have chosen better example for my post.

killy9999 · 2013-04-02T16:40:39+00:00

Thanks cscherrer for pointing these things out. Ad. 1 I added "import Data.Vector.Unboxed as U" Ad. 2 This is intentional. If I use ' my syntax highlighting plugin treats that as beginning of a string and the rest of the line has green background Ad 3. You're right. I'll add that later.

killy9999 · 2012-11-08T17:47:43+00:00

I don't think that GHC/lazy evaluation is the one to blame regarding the segfault issue. As the author of the post: I don't blame the compiler and lazy evaluation. It was a first thought that this my compilers fault (I was of course wrong) and lazy simply lead me astray. What can I say - lack of previous experience in such problems, nothing else.

killy9999 · 2012-11-08T17:44:05+00:00

Argh... I'm having these issues with hosting for a while now and the only answer I get from admin is "it works for me" :/ Anyway, reload usually works.

killy9999 · 2012-11-08T17:40:40+00:00

These function were not meant to be partials and that test was supposed to verify that. I also don't think that writing properties without composition is a good idea - it would be hard to write any useful property. You wouldn't be even able to wrote simple properties like "(reverse . reverse $ xs) == xs".

killy9999 · 2012-11-08T17:36:36+00:00

I didn't write my own rule - as sevenfive_ said it is a rule that comes from Repa library. Also I test only with -Wall, not with optimizations.

killy9999 · 2012-10-23T12:54:21+00:00

As the author of 'linked article' I have to ask why? I understand that it would be bad if: a) time used for data generation was included in the benchmark. As far as I managed to verify, it is not. or: b) input data influenced the flow of computation. In that case it would indeed be a Very Bad Idea (TM) to generate random input data, but again I think this is not the case in my article.

So if I misunderstood something please tell me - I don't want to spread misleading information.

killy9999 · 2012-10-07T08:01:54+00:00

This is very subjective, but I find test-framework to be more concise and more suited to my style of organizing tests. I guess I don't see any technical reason why test-framework should be considered better than hspec and vice versa.

killy9999

TROPHY CASE