Thank you, this is of some help.
Very useful to know putting pod in /* comments */ would do it.
I really appreciate your suggestion about t/, I will implement. Very classy solution.
Personally, putting pod in its own files has helped me maintain the code. It's a little tiny bit more a pain to have more files to keep track of.
I find that having the .pod files draws me to the fact that I have to document.
It helps me keep track of what the API is supposed to do.
I may write a .pod file as an idea and come back later to consolidate reality with plan.
It helps to have both code and doc open next to each other- to go back and forth- yes yes.. I know.. two windows on vi.. Somehow I'm still a mere mortal here.
What are some concrete reasons for which you suggest against the practice mentioned?
In reply to Re^2: Some clarification where pod files should reside in a distro
by leocharre
in thread Some clarification where pod files should reside in a distro
by leocharre
| For: | Use: | ||
| & | & | ||
| < | < | ||
| > | > | ||
| [ | [ | ||
| ] | ] |