Bird, that is part of what I was getting at also. In other languages I have seen interpreters [and/or] compilers slow drastically or even choke on long strings. Others, during lexical analysis, may run out of memory processing huge strings, (I believe I read Perl can use all available memory).
My questions about comments is because I have seen compilers that store programmer's comments in the binary, (use a bin/hex editor and check an .EXE ---look at the ascii, usually in the right-hand window of most editor). Since perl is interpreted, (as opposed to compiled), this would only exist in memory at run-time...
The Perl Style Guide link is great. Although Larry says, "Use here documents instead of repeated print() statements.", he does not give any reason ---- (but he is big daddy, so he don't have to)...
Ok, you and bird are in agreement --- (sort of) --- no need for anyone else to reply....<grin>
Part of the Perl Style guide from Larry reads; "Think about reusability...... Consider giving away your code. Consider changing your whole world view. Consider... oh, never mind."
This is my objective. I want to give my code away, but I don't want;
- to have to write 1000 lines of comments to explain why or how 100 lines of code works when my style of variable naming, code formatting and long-line splitting makes the code entirely readable with few comments needed.
- to have people who get the free code cry that they could "name that tune" (in 5 notes or less), when my verbose method works fine and is done to make the code easy to modify (e.g.- several short regex lines operating on the same string --- they could be combined, but aren't because that would make the entire mess change with any single change).