4 ms·
Suggested better title: A ToC of [Ian Lance Taylor's] 20 part linker essay
by rkangel 5y ago
Suggested better title:
A ToC of [Ian Lance Taylor's] 20 part linker essay
- gumby 5y agoI’ve only seen that notation (humans’ names in square brackets) on Hackaday. Is it used elsewhere?
- Ericson2314 5y agoIf this is some parse-trees-for-nerd-readers things, it really should be [...]'s. I always do ". for quotes within the sentence too. The lisper in me won't let it be otherwise.
- rkangel 5y agoThe notation I'm using isn't as specific as 'human name in square brackets'. It's the more standard approach editorial approach used to add context when pulling out a quote. If you read the original text the context would be obvious but with the quote on its own it doesn't make sense so you want to add that context back in. That's done in square brackets to indicate that it is added and not part of the original quote.
- jcranmer 5y agoThe syntax is used where you're quoting text, but you're replacing some text with other text for explanatory purposes. So, for example, if the original quote was: > The majority, however, uses this factor to create a distinction between declaring and implementing code that in effect removes copyright protection from declaring code. Standing alone, you might not realize what "this" refers to. Instead, you'd substitute an explanation: > The majority, however, uses [the nature of copyrighted work] factor to create a distinction between declaring and implementing code that in effect removes copyright protection from declaring code. In practice, one of the most common replacements is replacing a pronoun with a name. So "his" becomes "[John Doe's]".