comment on

I think the problem Abigail addresses with Inside Out Objects is, although similar, a very different issue.

There are several issues they address. I'm specifically talking about just one of them.

That's really a convention and it is often not followed.

What he's saying is that it should be followed if you want to make your life easier.

I don't know what to say about his POST requests must always result in redirects idea...

Well, keeping in mind that it is assumed that your GETs never change server state, then it makes a lot of sense considering the problem he is trying to address.

Yes, I saw that he rolled his own templating system. I was irked as well. I didn't review the code, no.

Note that if you think I "accused" you of writing C-ish Perl, then at the same time I "accused" myself of writing LISP-ish Perl. I was simply commenting on our preferences.

Makeshifts last the longest.

In reply to Re^2: Falling for the same trap - since 1942 by Aristotle
in thread Falling for the same trap – since 1942 by Aristotle

Are you posting in the right place? Check out Where do I post X? to know for sure.
Posts may use any of the Perl Monks Approved HTML tags. Currently these include the following:
<code> <a> <b> <big> <blockquote> <br /> <dd> <dl> <dt> <em> <font> <h1> <h2> <h3> <h4> <h5> <h6> <hr /> <i> <li> <nbsp> <ol> <p> <small> <strike> <strong> <sub> <sup> <table> <td> <th> <tr> <tt> <u> <ul>
Snippets of code should be wrapped in <code> tags not <pre> tags. In fact, <pre> tags should generally be avoided. If they must be used, extreme care should be taken to ensure that their contents do not have long lines (<70 chars), in order to prevent horizontal scrolling (and possible janitor intervention).
Want more info? How to link or How to display code and escape characters are good places to start.


The stupid question is the question not asked
	PerlMonks