Stanislav Malyshev <smalys...@gmail.com> wrote: > > Something I am missing here. RFC is talking about removing indents from > heredoc text, but the vote says "Allow for the closing marker to be > indented?" and does not mention that indenting closing marker also > changes how the rest of the heredoc is parsed. Is this still the case?
>From the body of the RFC: "To enable for the closing marker to be indented, ... The indentation of the closing marker dictates the amount of whitespace to strip from each line within the heredoc/nowdoc" That's about 3 lines of text into the RFC. Presumably the RFC didn't think the whole concept being voted on needed to be repeated in the voting option. Perhaps it should have been but: Christopher Jones wrote: > I'm going to have to assume so and vote No. It is better to ask questions during the discussion phase of an RFC, but if you do have a question during the voting period, you're still allowed to ask rather than voting based on assumptions. > PS. RFC writers: please take care when writing specs. Please don't use passive aggressive 'helpful hints' like this. For example: "RFC voters - please read the RFC during the RFC period and ask questions then. ;-)" is an irritating way of writing this. A way of writing it that is more conducive to a productive discussion is: I think this is covered in the RFC text. Does the line I picked out above, give a clear description for what that vote is for? cheers Dan Ack -- PHP Internals - PHP Runtime Development Mailing List To unsubscribe, visit: http://www.php.net/unsub.php
