3 ms·

spoiler: the `l` is for long. the previous `seek()` took an int. i rather enjoy the exposition of the article. he weaved the story nicely rather than just blur

spoiler: the `l` is for long. the previous `seek()` took an int. i rather enjoy the exposition of the article. he weaved the story nicely rather than just blurt out the answer. the utoronto unix blog in general is enjoyable.

n6h6 3y ago
I am curious why you yourself have "blurted out the answer" if you enjoyed the opposite from the article? This isn't a callout or anything, I'm just genuinely curious.
- jiveturkey 3y ago
  well i prefaced it with "spoiler". i probably could have made a stronger warning. it's useful in general in a forum like this, for people that just want the answer. like when a news or blog article has a question in the headline to make you wade through the ads to get to the main point. not too different to how it's useful when people post a paywall bypass link. sure, anyone can just figure that on their own, but it's useful to simply have a link right here on HN, or a summary or abstract of an article. so that was my thinking. that the very large majority don't care and would benefit from just having the answer. i tried to encourage reading the blog anyway, even after knowing the answer. you know what, let me edit the answer out. i think you're right. if you don't care you don't care so why ruin the article. damn. too late to edit.
pjmlp 3y ago
And then it became lseek64(), when longs weren't no longer big enough.
- usr1106 3y ago
  So llseek would have been logical. But maybe being informative and portable is better. Edit: actually llseek exists internally: https://www.man7.org/linux/man-pages/man3/lseek64.3.html https://www.man7.org/linux/man-pages/man3/lseek64.3.html
  - pjmlp 3y ago
    On Linux.
maxparay 3y ago
"the utoronto unix blog in general is enjoyable" Didn't know it was called the utoronto unix blog. I've always called it CSpace like the author calls it here: https://utcc.utoronto.ca/~cks/space/FrontPage https://utcc.utoronto.ca/~cks/space/FrontPage

n6h6 3y ago

I am curious why you yourself have "blurted out the answer" if you enjoyed the opposite from the article? This isn't a callout or anything, I'm just genuinely curious.

jiveturkey 3y ago
well i prefaced it with "spoiler". i probably could have made a stronger warning. it's useful in general in a forum like this, for people that just want the answer. like when a news or blog article has a question in the headline to make you wade through the ads to get to the main point. not too different to how it's useful when people post a paywall bypass link. sure, anyone can just figure that on their own, but it's useful to simply have a link right here on HN, or a summary or abstract of an article. so that was my thinking. that the very large majority don't care and would benefit from just having the answer. i tried to encourage reading the blog anyway, even after knowing the answer. you know what, let me edit the answer out. i think you're right. if you don't care you don't care so why ruin the article. damn. too late to edit.

pjmlp 3y ago

And then it became lseek64(), when longs weren't no longer big enough.

usr1106 3y ago
So llseek would have been logical. But maybe being informative and portable is better. Edit: actually llseek exists internally: https://www.man7.org/linux/man-pages/man3/lseek64.3.html https://www.man7.org/linux/man-pages/man3/lseek64.3.html
- pjmlp 3y ago
  On Linux.

maxparay 3y ago

"the utoronto unix blog in general is enjoyable" Didn't know it was called the utoronto unix blog. I've always called it CSpace like the author calls it here: https://utcc.utoronto.ca/~cks/space/FrontPage https://utcc.utoronto.ca/~cks/space/FrontPage