Re: heredoc and coding standards

Rob, I've come across the same dilema. To keep things clean while using the convenience of heredoc you can write the heredoc in a seperate file and include_once() the file. Larry Rob Day <rday@tsl.state.tx.us> wrote: > I try to write very clean code. However, there is one thing that always bugs > me - using heredoc syntax in a function. Code in the function really should > be indented (or 4 spaces for PEAR types), but, to quote the documentation, > "the closing identifier must begin in the first column of the line." That > means no tabs, right? So is that just the way it is? Do I just need to not > worry about my tabs for heredoc? Is there some way to maintain consistency > without breaking my code? > -Rob