marvy

12 ms·

1. 61.▲
   by marvy 6y ago

   Just read your rant/blogpost. You didn't give too many examples of what's wrong with LaTeX, but you did mention putting two images next to each other. Isn't this just: \includegraphics{img1} \includegraphics{img2} Or i
2. 62.▲
   by marvy 6y ago

   Let's take an example: https://arxiv.org/pdf/1606.06389.pdf A cursory inspection seems to indicate ctrl-F is fine here? Or am I missing something?
3. 63.▲
   by marvy 6y ago

   I assumed that if ctrl-F works, then screen readers also work. Can you share a bit of information about what tends to go wrong, and/or how document authors can fix it?
4. 64.▲
   by marvy 6y ago

   You probably stopped checking that thread by now, but I finally replied to your comment from the day before yesterday: https://news.ycombinator.com/item?id=23306317
5. 65.▲
   by marvy 6y ago

   You're tangling a bunch of stuff together in a confusing mess. Let's take one thing at a time. 1. You're right that you can't use the & operator on a variable that was declared using the register keyword. 2. However
6. 66.▲
   by marvy 6y ago

   So it turns out I'm kind of wrong! My arguments for jumping "inward" still seem pretty valid, but they don't generalize to jumping "outward". And indeed, GCC actually allows this, but you need to use the righ
7. 67.▲
   by marvy 6y ago

   Using computed goto would (probably) make the code compile, but it wouldn't actually work. That's would be heading directly into undefined behavior territory (aka land of the nasal demons). To give just one or two examples of why
8. 68.▲
   by marvy 6y ago

   You can actually get rid of the confusing nesting: switch(n%4) { loop: case 0: stuff(); case 3: stuff(); case 2: stuff(); case 1: stuff(); if(--n) goto loop; }
9. 69.▲
   by marvy 6y ago

   What's not worth it? Loop unrolling? Something else?
10. 70.▲
    by marvy 6y ago

    Me too. I suspect this was intentional :)
11. 71.▲
    by marvy 6y ago

    That actually makes sense! Cool!
12. 72.▲
    by marvy 6y ago

    Wow. The fact that you care about this being stable implies that you plan to use this "for real"; the fact that you actually implemented this implies you care enough to put in some real work. So you must have a use case in mind,
13. 73.▲
    by marvy 6y ago

    So, at first I thought this approach is doomed, because you lose comments, and what looks like a comment to Rust may not look like one to Python. Example: x = y // 2 # floor division But then I decided to look at the docs:
14. 74.▲
    by marvy 6y ago

    It seems AFL might have been ported to Windows: https://github.com/ivanfratric/winafl (don't know; just found this two minutes ago)
15. 75.▲
    by marvy 6y ago

    thanks
16. 76.▲
    by marvy 6y ago

    I don't follow Scala (never wrote a single line), so I didn't realize the company changed names from Typesafe to Lightbend. Here's a question: how on earth do they make any money? The Wikipedia article makes an offhand ment
17. 77.▲
    by marvy 7y ago

    but this book started with a relatively small scope too
18. 78.▲
    by marvy 7y ago

    Also useful in the other direction: your code works now, but in C++17 that's a keyword so you'll have to rename it.
19. 79.▲
    by marvy 7y ago

    Good question. Do we have a plentiful supply? Any one know?
20. 80.▲
    by marvy 7y ago

    :)
21. 81.▲
    by marvy 7y ago

    seek not to comprehend the downvoters, for it is written: it is simpler to predict each gust of wind in a storm, than to explain even a single downvote or something
22. 82.▲
    by marvy 7y ago

    maybe you're thinking of unrecognized escape sequences? E.g., printf("Hello \m") is undefined.
23. 83.▲
    by marvy 7y ago

    Tsk, tsk. Replications, Replications, Replications! ;)
24. 84.▲
    by marvy 7y ago

    This time I think its the first one :)
25. 85.▲
    by marvy 7y ago

    But realistically it can't go on much longer, right? The diameter of a silicon atom is like 0.21 nanometers, so we're almost within an order of magnitude from rock bottom, right? I don't actually know anything about this st
26. 86.▲
    by marvy 7y ago

    thanks!
27. 87.▲
    by marvy 7y ago

    Does this picture change much between the 32-bit vs 64-bit world? How about if there are few vs many threads? (For instance, if a program on 32-bit windows spawns hundreds of threads, surely you can't squeeze all those stacks below t
28. 88.▲
    by marvy 7y ago

    That makes sense, thanks! So it's a bit over-cautious.
29. 89.▲
    by marvy 7y ago

    when would console() be wrong?
30. 90.▲
    by marvy 7y ago

    you're saying this never happens? or rarely? or just not always? or you object to the word "tomorrow"? or...?