On 05/03/2012 09:06 AM, John SJ Anderson wrote:
I'm really quite intrigued by the assertion that CGI is very seldom used.
There are two senses of "CGI" that are being conflated here. There's
CGI-the-protocol -- i.e., dynamic web content -- which is used all the time all over the
place. And there's also CGI-the-Perl-module a/k/a CGI.pm -- which isn't used all that
much anymore by people who do a lot of web programming.
You can do CGI in Perl without using CGI.pm.
Okay, I can understand that. Point me in the right direction for this.
I don't really want to learn about steam engines if gas combustion
engines are 'the thing'. I suppose that's been my point all along.
Based on this entire thread, the Template Toolkit is used entirely for
building websites in perl.
I'm sorry you've gotten that impression, but that's incorrect. TemplateToolkit
is a generic templating framework. It can be used for anything involving a
template plus some data producing some output.
Even in the cases where it is used in a web programming context,
TemplateToolkit may not be producing *HTML*. My current work project is a web
application. It uses TemplateToolkit exclusively -- but it produces HTML
output, XML output, and sends email. All generated using TemplateToolkit.
Okay, perhaps that was hyperbole on my part. Although, honestly, I
included all the other things websites can do not just output HTML.
But, it appears that I'm getting contradictory messages here, none of which
make me feel particularly comfortable with continuing to use perl for my
project.
I'm sorry you're not having the best experience getting your questions answered on the
list. I really am. I've considered jumping into this thread before, but I've been very
busy with work and I was hoping things would straighten out on their own. Seems that
isn't happening, and again, I apologize. That said, this thing you've done, a couple
times now, of "I'm just gonna leave and go use PHP" -- that's not helping you
to get better answers.
If you can solve your problem more quickly and easily using PHP, by all means, use PHP. (And feel free to substitute "Python" or
"Ruby" or "Haskell" or "Java" or "Scala" or "cuneiform tablets" in for "PHP" in that
sentence.)
This list isn't about evangelizing or advocating for the use of Perl; it's about helping
people who have decided to use Perl to use it effectively, to enjoy using it, and to use
it "properly" -- in that order. (The scare quotes around properly are there
because this is Perl and our motto is TIMTOWTDI.)
Again, you're probably right, I should leave that bit out of the
replies. I really want to build this entirely in perl. Too much of the
existing code is pure perl. Maybe I hadn't made that clear throughout
the posts I put on this list. If that's the case, that's my mistake,
and should certainly not be any indictment of anyone misunderstanding my
problem.
I'm being given the impression that perl isn't used the way I'm intending to
use it.
This was really more of a point that in some cases I've been told 'don't
do this', or 'it's not done this way' without any real explanation for
/why/ it's not done that way, or at least get me to resources that do so.
No one is here to solely hold my hand. I am well aware of that, which
is why I've asked not just for a solution, but additional places I can
do my own research. There's nothing more frustrating that hearing 'don't
do this' without knowing why not.
Based on the description you have given of your problem, it could easily be
solved with Perl.
Part of the problem here is that you seem to have latched onto a particular
approach to solving your problem, and you are not terribly open to hearing that
the approach you have selected is not the best approach *if your tool of choice
for solving the problem is Perl*.
Rather that phrasing things as "here's my problem, here's my approach, how do I do that
approach with Perl?", consider phrasing them as "here's my problem, how should I approach
that if Perl is my tool?"
I see your point with this, but to my mind it's two sides of the same
coin. However, I will certainly keep this in mind as I craft any future
posts. Sometimes, phrasing is more important than anything else.
I appreciate the time taken for you to reply. As it is, please point me
to how I can get perl to do CGI without CGI.pm. I'm actually quite
curious about how to do this as /why/ the move away from the module in
the first place. (Although the latter is completely irrelevant other
than for my personal curiosity.)
Any resources out on the web about this will be greatly appreciated.
--
Mark Haney
Software Developer/Consultant
AB Emblem
ma...@abemblem.com
Linux marius.homelinux 3.3.2-6.fc16.x86_64 GNU/Linux
--
To unsubscribe, e-mail: beginners-unsubscr...@perl.org
For additional commands, e-mail: beginners-h...@perl.org
http://learn.perl.org/
