Raiph Mellor hyperpunned:
> With this whiny man exchange ultimately having bourne supreme fruit,
> the apocalypse watch for the post damian weekend begins...
ARRRG!
Damian ;-)
> Excellent idea. But may I suggest you perhaps might like to hold off
> that discussion until next week?
>
> @Larry had some very fruitful discussions about the long-overdue Pod
> spec during YAPC::EU last week and, as a result, I plan to (finally!!!)
> release a new version of S26 this week-end.
Raiph Mellor wrote:
> Anyhoo, I'd love to see a session of brainstorming, with nitty gritty
> detail, about possible ways to get what you guys and Mark and I and
> perhaps others think we would like to see in the way of super tightly
> woven together comments and code, where said brainstorming in
On Thu, Aug 13, 2009 at 1:00 AM, Darren Duncan wrote:
> Timothy, you raise a good point...
> [discussion]
> I think this can be made to work without much fuss
I'm curious about these sorts of conversations, and the way the
community works in relation to them.
I'm also curious about this specific
Timothy, you raise a good point that I had been thinking about earlier as a
consequence of my proposal about comments being preserved and attached as
meta-data to what is most appropriate contextually.
I'm thinking that it should be formally defined somewhere (maybe as an extra
section in the
I had an interesting idea I wanted to put out there. If I'm being a
good boy and commenting my code, I do things like the following pseudocode:
# Get the stuff and do other stuff with it
@lines = slurp("file");
@otherlines = map { s/foo/bar/ } @lines
putfile("fi
Eirik Berg Hanssen wrote:
Moritz Lenz writes:
In all other cases of quote like constructs are the semantics are
explicit first (think of Q, qx, m, <, «), the delimiter comes later.
Changing that all of a sudden seems very unintuitive and wrong.
Thing is, comments are not quote-like. All of
