e substitution doesn't work. Clear as Mud?? Any ideas?
Once I fixed an issue like this (because it suited the problem
well) by checking to see how many values I got back from the
split and doing things based on that number; perhaps that
would work for you.
Dave
--
Dave Newton, [EMAIL PROTECTED]
;}};
= instead of eq (string comparison), and in any case even
using the wrong operator you'd have wanted == (equality
test) instead of = (assignment operator).
Just to start a formatting flamefest ;) I would have written
this like this:
if ($ENV{'HTTP_REFERER'} eq "") {
> > So yes, I take newlines in paths seriously. You can't be an ostrich
> > about them burying your head in the sand. That's not secure, and you
> > will be hacked.
>
> Ostriches don't really bury their heads in the sand, you know...
S, that was supposed to be a secret.
I've not been able
> ([EMAIL PROTECTED]) spew-ed forth:
> > I've not been able to come up with any reasonable CGI that would be
> > creating a path that the user has any control over; why would one want
> > to do that?
> What about things like document/filesystem management tools? Or
> (re)configuration tools? Sayin
Bear in mind that without any sort of delay it's unlikely
you'll be able to see any of this occuring.
Ah, the good old days, where a 300-baud modem was fast
and little spinny cursors were still interesting. *sigh*
Dave
--
Dave Newton, [EMAIL PROTECTED]
> OK, I had to try the two ways again to see how much difference it made. I
> created a random contents fixed field file 14500 lines long X 80 columns
> wide, and tried processing the lines (using substr($_,)to
> break lines up into 4 sections, substitute based on a few patterns, and
change a
> He'd never seen the spinny cursor and was quite impressed - quite sad
really!
*grin*
I'll admit they're cute :)
Great story though; I'll have to remember that as an easy way to impress
people.
Dave
Kurt Edmiston said:
> Coming from C++-land, I've always been taught over and over again
> that all subroutines/functions/blocks/etc should have only a single
> entry point and a single exit point.
Works great in theory ;) Especially if you have exceptions.
It's just not practicle/readable to alw
I'm continually surprised by the information-free subject headers. Most
people
that start a new thread here need help; that's why they're here. Not
flaming,
just hoping that people will take into account the potential usefulness of
subject lines (i.e., "Oooo, I know how to do that!" or "Oooo, I ne
> Still no dice! I keep getting errors:
>
> C:\Perl>ppm
> PPM interactive shell (2.1.5) - type 'help' for available commands.
> PPM> set
> Commands will be confirmed.
> Temporary files will be deleted.
> Download status will be updated every 16384 bytes.
> Case-insensitive searches will be perform
>> (Original two choices)
>> : Is it better to :
> > :
> > : %Fields = %{$Accts{$account}};
> > : foreach $name ( keys %Fields ) {
> > : print "$name : $Fields{$name}\n";
> > : }
> > :
> > : or
> > :
> > : foreach $name ( keys %{$Accts{$account}} ) {
> > : print "$name : \n";
> > : }
> I
> Where can I get more information on How to test(QA) Website
> or client server application using Perl-win32::GuiTest.
My understanding was that win32::guitest was for testing
windows applications, not websites?
Dave
--
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, e-ma
12 matches
Mail list logo
