Re^3: How to escape square bracket in PM?

Eh, why? What's wrong with just using the html entities.. which already work? I suppose you save a character or two, but hell, we're using html, which isn't known for it's concise mark up. Tye has already pointed out the ridiculous amount of work needed to implement this change that merely saves a character.

Comment on Re^3: How to escape square bracket in PM?

Replies are listed 'Best First'.
Re^4: How to escape square bracket in PM? by Tanktalus (Canon) on Apr 13, 2005 at 00:34 UTC
What's wrong with just using the HTML entities? Rather than using [cpan://File::Spec], just use <a href="http://search.cpan.org/search?mode=module&query=File%3A%3ASpec">File::Spec</a>. Or, instead of using magic <code> tags, just manually escape all the special characters in your code. Someone made the horrific mistake of getting us hooked on this HTML-for-dummies approach of writing on this site, in ways that made sense for perl programmers. dragonchild's question is just along the same lines as everything else we have here to make our lives easier in things we do all the time (refer to documentation, CPAN, ISBNs, other nodes, other users, other sites, etc.). One thing we do all the time is put brackets (square brackets for those who prefer) in our text. It's not unreasonable to request it. And I'm not sure it's a ridiculous amount of work. A significant amount of work, yes. But I'm not so sure about ridiculous. The amount of work is hugely dependant on the specification. If we need to now go and escape all backslashes, yes, that's ridiculous. Maybe more. If we come up with an idea that is a bit more compact, then it may not be nearly as bad. It's not as easy as, say, changing where doc:// tags or cpan:// tags point at. But it's just a matter of finding all the places that link handling is called, and mucking about with the substitution regular expression a bit.	[reply]

Replies are listed 'Best First'.

Re^4: How to escape square bracket in PM?
by Tanktalus (Canon) on Apr 13, 2005 at 00:34 UTC

What's wrong with just using the HTML entities? Rather than using [cpan://File::Spec], just use <a href="http://search.cpan.org/search?mode=module&query=File%3A%3ASpec">File::Spec</a>. Or, instead of using magic <code> tags, just manually escape all the special characters in your code.

Someone made the horrific mistake of getting us hooked on this HTML-for-dummies approach of writing on this site, in ways that made sense for perl programmers. dragonchild's question is just along the same lines as everything else we have here to make our lives easier in things we do all the time (refer to documentation, CPAN, ISBNs, other nodes, other users, other sites, etc.). One thing we do all the time is put brackets (square brackets for those who prefer) in our text. It's not unreasonable to request it.

And I'm not sure it's a ridiculous amount of work. A significant amount of work, yes. But I'm not so sure about ridiculous. The amount of work is hugely dependant on the specification. If we need to now go and escape all backslashes, yes, that's ridiculous. Maybe more. If we come up with an idea that is a bit more compact, then it may not be nearly as bad. It's not as easy as, say, changing where doc:// tags or cpan:// tags point at. But it's just a matter of finding all the places that link handling is called, and mucking about with the substitution regular expression a bit.

[reply]