Timeline for Tweetable Mathematical Art
Current License: CC BY-SA 3.0
16 events
| when toggle format | what | by | license | comment | |
|---|---|---|---|---|---|
| Apr 13, 2017 at 12:39 | history | edited | CommunityBot |
replaced http://codegolf.stackexchange.com/ with https://codegolf.stackexchange.com/
|
|
| Aug 21, 2014 at 13:36 | comment | added | stderr | Beautiful unreadable code. <3 | |
| Aug 12, 2014 at 18:25 | history | edited | FireFly | CC BY-SA 3.0 |
Add Bub
|
| Aug 12, 2014 at 18:19 | history | edited | FireFly | CC BY-SA 3.0 |
Add Bub
|
| Aug 12, 2014 at 2:34 | comment | added | DreamWarrior | @FireFly; that's probably why. I used the unsigned char version, which explains why I had fewer gradients. When I tried the unsigned short version I didn't put back the htons stuff because some posts relied on its not being there.... Too bad there are three different versions now, lol -- unsigned char, unsigned short (incorrect output format), and unsigned short (correct output format w/ htons). Guess I have to start trying them all for the answers that interest me, lol. | |
| Aug 11, 2014 at 20:16 | comment | added | FireFly |
@DreamWarrior I have edited the shim to use htons to output big-endian intensities, per a comment to the question--that's probably the issue. I dunno why the shim in the OP doesn't use htons considering most people would use little-endian machines.
|
|
| Aug 11, 2014 at 20:02 | comment | added | DreamWarrior | @FireFly; I'm using 32bit x86 Linux (an old Redhat machine). So, sizeof(long) is 4, same as sizeof(int). To get a 64bit integer in 32bit you must use "long long" (hence the need for LL). My output looks similar, but the color intensities are off -- see i.imgur.com/ULGOZ1Z.jpg. | |
| Aug 11, 2014 at 19:09 | comment | added | FireFly |
@DreamWarrior that's probably true. What platform are you on? I'm on Linux x86_64, but I checked earlier and for me sizeof(int) is still 4 so I'm not sure how it's different from a "usual" 32-bit setup. I think my code should work as long as sizeof(long) is ≥8, but honestly I'm not very sure. What output do you get?
|
|
| Aug 11, 2014 at 17:47 | comment | added | DreamWarrior | Neat, I like how you took the 8x8 pixel art and "resized" it on the fly. However, I had to make a few changes and I'm still not getting exactly your image. I changed the 1L and 255L to 1LL and 255LL. Since that made it better, I am assuming you're probably compiling in 64bit mode and there's some bit width issues making the rest of my image come out wrong. But, still, nice job! | |
| Aug 11, 2014 at 8:44 | comment | added | FireFly | @MartinBüttner oops, you're correct. I fixed it and made another update to the functions. | |
| Aug 11, 2014 at 8:43 | history | edited | FireFly | CC BY-SA 3.0 |
Make better use of free space, fix up code
|
| Aug 11, 2014 at 1:37 | comment | added | trichoplax is on Codidact now | This is incredibly short now. Could you fit one of these bit patterns into the texture in your raycasting answer...? | |
| Aug 11, 2014 at 1:22 | history | edited | FireFly | CC BY-SA 3.0 |
Golfed & with "border"
|
| Aug 10, 2014 at 23:49 | comment | added | FireFly | Yup, there's plenty of tricks to pull to reduce the size. I might give a go at extending it tomorrow. | |
| Aug 10, 2014 at 23:45 | comment | added | trichoplax is on Codidact now | I love this. Plenty of room to add extra features too... | |
| Aug 10, 2014 at 23:35 | history | answered | FireFly | CC BY-SA 3.0 |
