4 ms·
> Yet you have to know both versions of them all, and be able to recognize and understand both kinds when reading other people's code. You have to be able to u
by perigrin 7y ago
> Yet you have to know both versions of them all, and be able to recognize and understand both kinds when reading other people's code.
You have to be able to understand that if it's a two character variable of all punctuation you may need to look it up to figure out what it is. Typing `!perldoc $"` into duck duck go sent me to https://perldoc.pl/variables/$%22 https://perldoc.pl/variables/$%22 ... which is roughly equivalent to `!g [docker error]` which I already do all day long.
- marcosdumay 7y ago$ perldoc '$' No documentation found for "$" I hope perldoc search improved on Perl6, because it only used to match section titles, and none of the line noise vars are there. (Yes, after a while one should learn yo search for the section that explains all the vars, at least if he's coding Perl all day. But it's a ton of useless trivia to keep in mind anyway.)
- Grinnz 7y agoThe correct invocation to search for a variable named $" (not $) is perldoc -v '$"', which the variable search on perldoc.pl was modeled after. A glance at "man perldoc" (or "perldoc perldoc") will tell you of the very useful other switches, such as -f and -q.