Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Re: hyperoverquoting of built-in functions: JUST SAY NO #81

Closed
p5pRT opened this issue Jun 19, 1999 · 1 comment
Closed

Re: hyperoverquoting of built-in functions: JUST SAY NO #81

p5pRT opened this issue Jun 19, 1999 · 1 comment

Comments

@p5pRT
Copy link
Collaborator

@p5pRT p5pRT commented Jun 19, 1999

Migrated from rt.perl.org#884 (status was 'resolved')

Searchable as RT884$

@p5pRT
Copy link
Collaborator Author

@p5pRT p5pRT commented Jun 19, 1999

From @Abigail

What is so bad in using 2? After all​:

Pod is supposed to be a clean easy way for mere mortals to write
documentation. The twin goals are easy of writing and easy of parsing.

Ease of writing. Why should I have to remember which shortcuts the various
translators are supposed to have, and which they don't?

That 1 works is great, but that doesn't make 2 wrong.

Abigail

@p5pRT p5pRT closed this Nov 28, 2003
karenetheridge added a commit that referenced this issue Nov 2, 2019
  [DELTA]

5.20191102  2019-11-02 05:34:43Z
  * fix bad pod markup in perlfaq8 (PR #78; thanks, Joaquín Ferrero!)
  * remove stale section about lib.pm (PR #82, Dan Book)
  * update perlfaq9 to reference Email::Stuffer (PR #79, Dan Book)
  * update perlfaq9 to reference URL::Search (PR #80, Dan Book)
  * update perlfaq9 to use HTTP::Tiny (PR #81, Dan Book)
  * fix some broken links (issue #71, dctabuyz)
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Projects
None yet
Linked pull requests

Successfully merging a pull request may close this issue.

None yet
1 participant
You can’t perform that action at this time.