[31853] in Perl-Users-Digest
Perl-Users Digest, Issue: 3116 Volume: 11
daemon@ATHENA.MIT.EDU (Perl-Users Digest)
Sat Sep 4 21:09:24 2010
Date: Sat, 4 Sep 2010 18:09:08 -0700 (PDT)
From: Perl-Users Digest <Perl-Users-Request@ruby.OCE.ORST.EDU>
To: Perl-Users@ruby.OCE.ORST.EDU (Perl-Users Digest)
Perl-Users Digest Sat, 4 Sep 2010 Volume: 11 Number: 3116
Today's topics:
Ideal data structure for nested list format? <tuxedo@mailinator.com>
Re: Ideal data structure for nested list format? <ben@morrow.me.uk>
Re: Ideal data structure for nested list format? <tuxedo@mailinator.com>
Re: Ideal data structure for nested list format? <uri@StemSystems.com>
Re: Ideal data structure for nested list format? <tuxedo@mailinator.com>
Re: Ideal data structure for nested list format? <ben@morrow.me.uk>
Re: Multidimensional array <tadmc@seesig.invalid>
Re: Multidimensional array <paul@pstech-inc.com>
Re: Multidimensional array <sbryce@scottbryce.com>
Re: Multidimensional array <uri@StemSystems.com>
Re: Multidimensional array <paul@pstech-inc.com>
Digest Administrivia (Last modified: 6 Apr 01) (Perl-Users-Digest Admin)
----------------------------------------------------------------------
Date: Sat, 4 Sep 2010 20:40:56 +0200
From: Tuxedo <tuxedo@mailinator.com>
Subject: Ideal data structure for nested list format?
Message-Id: <i5u3ro$cdu$02$1@news.t-online.com>
In trying to construct a nested html list with perl I have some questions
what the ideal data structure may be for the specific purpose.
The menu is generated on the fly for each page request. The script lives in
a perl file named menu.pl and the current page that is accessed is known to
the script via a server environment variable accessible in a $current_page
perl variable. The html parts are imported onto individual html pages
through SSI (includes) and all pages are placed at a root level, so there
are no sub-directories or chances of any pages having a same name.
This is a simplified html output of the menu in an unordered list format:
<ul>
<li><a href=1.1.html>Level 1.1</a>
<ul>
<li><a href=2.1.html>Level 2.1</a></li>
<li><a href=2.2.html>Level 2.2</a>
<ul>
<li><a href=3.1.html>Level 3.1</a></li>
<li><a href=3.2.html>Level 3.2</a></li>
</ul>
</li>
<li><a href=2.3.html>Level 2.3</a></li>
</ul>
</li>
</ul>
So there are three levels and the first two levels have nested lists
within. If for example page 3.2.html is accessed, the script should write
out that <li> entry *without* the enclosing <a href=3.2.html>..</a> parts,
as well as add a css-class to that one list item: <li class=current_page>.
The script should know its nearest parent <li> item, so in case of
accessing page 3.2.html, that would be the <li> with the 2.2.html link.
This entry should then have have the css-class: <li class=parent_level_2>.
Additionally, the second nearest parent should be given another css-class,
such as <li class=parent_level_1> (so it may be styled differently).
If the current page is one that does not exist in the menu, although the
menu has been imported on such a page, then no special classes or non-link
formatting is needed for any of the array entries. The html output would
just appear exactly as the above example.
Without the actual link names, I guess the list may be constructed with a
LoL or an AoA, such as:
my @AoA = ('1.1.html',
['2.1.html',
'2.2.html',
['3.1.html',
'3.2.html'],
'2.3.html']);
If so, a parallel AoA's would be needed for the link names to be combined
in a final loop. Or is some other data structure better suited for the
purpose? I.e.: sticking all items together in a nested html list in order
of entry in the perl code, as well as figure out the opening parent <li>
points (if any) in order to apply custom css-classes to relevant <li>'s.
Looking at perldsc, in addition to AoA, alternatives such as HoA, AoH, HoH
as well as some more elaborate data structures exist. I'm not sure what's
best? The maintenance of the link list will involve changing or updating
entries only very occasionally, so it can be done in separate arrays in
case that's better. Anyway, it's not important how, as long as it works...
What is the ideal data structure for the particular hierarchial list
functionality and where the described level specific output can easily be
incorporated?
Many thanks for any advise or general pointers.
Tuxedo
------------------------------
Date: Sat, 4 Sep 2010 20:46:47 +0100
From: Ben Morrow <ben@morrow.me.uk>
Subject: Re: Ideal data structure for nested list format?
Message-Id: <7akal7-urk.ln1@osiris.mauzo.dyndns.org>
Quoth Tuxedo <tuxedo@mailinator.com>:
> In trying to construct a nested html list with perl I have some questions
> what the ideal data structure may be for the specific purpose.
>
> The menu is generated on the fly for each page request. The script lives in
> a perl file named menu.pl and the current page that is accessed is known to
> the script via a server environment variable accessible in a $current_page
> perl variable. The html parts are imported onto individual html pages
> through SSI (includes) and all pages are placed at a root level, so there
> are no sub-directories or chances of any pages having a same name.
>
> This is a simplified html output of the menu in an unordered list format:
>
> <ul>
> <li><a href=1.1.html>Level 1.1</a>
> <ul>
> <li><a href=2.1.html>Level 2.1</a></li>
> <li><a href=2.2.html>Level 2.2</a>
> <ul>
> <li><a href=3.1.html>Level 3.1</a></li>
> <li><a href=3.2.html>Level 3.2</a></li>
> </ul>
> </li>
> <li><a href=2.3.html>Level 2.3</a></li>
> </ul>
> </li>
> </ul>
>
> So there are three levels and the first two levels have nested lists
> within. If for example page 3.2.html is accessed, the script should write
> out that <li> entry *without* the enclosing <a href=3.2.html>..</a> parts,
> as well as add a css-class to that one list item: <li class=current_page>.
>
> The script should know its nearest parent <li> item, so in case of
> accessing page 3.2.html, that would be the <li> with the 2.2.html link.
> This entry should then have have the css-class: <li class=parent_level_2>.
>
> Additionally, the second nearest parent should be given another css-class,
> such as <li class=parent_level_1> (so it may be styled differently).
>
> If the current page is one that does not exist in the menu, although the
> menu has been imported on such a page, then no special classes or non-link
> formatting is needed for any of the array entries. The html output would
> just appear exactly as the above example.
>
> Without the actual link names, I guess the list may be constructed with a
> LoL or an AoA, such as:
>
> my @AoA = ('1.1.html',
> ['2.1.html',
> '2.2.html',
> ['3.1.html',
> '3.2.html'],
> '2.3.html']);
>
> If so, a parallel AoA's would be needed for the link names to be combined
> in a final loop. Or is some other data structure better suited for the
> purpose? I.e.: sticking all items together in a nested html list in order
> of entry in the perl code, as well as figure out the opening parent <li>
> points (if any) in order to apply custom css-classes to relevant <li>'s.
I would start with this:
my @pages = (
{ page => "1.1.html", title => "Level 1.1", children => [
{ page => "2.1.html", title => "Level 2.1" },
{ page => "2.2.html", title => "Level 2.2", children => [
{ page => "3.1.html", title => "Level 3.1" },
{ page => "3.2.html", title => "Level 3.2" },
] },
{ page => "2.3.html", title => "Level 2.3" },
] },
);
and then build a hash of 'parents', like so
sub populate_parents;
sub populate_parents {
my ($parents, $pages, $parent) = @_;
for (@$pages) {
my $page = $_->{page};
push @{$parents->{$page}}, $parent;
my $kids = $_->{children};
$kids and populate_parents $parents, @$kids, $page;
}
}
my %parents;
populate_parents \%parents, \@pages, undef;
This will give you a data structure like
%parents = (
"1.1.html" => [undef],
"2.1.html" => [undef, "1.1.html"],
"3.1.html" => [undef, "1.1.html", "2.2.html"],
...
);
Then, given a page name, you can build another hash
my $page = "3.1.html";
my $parents = $parents{$page};
my %class =
map +($parents->[$_] => "parent_level_$_"),
grep defined $parents->[$_],
0..$#$parents;
which will let you look up the required class name as you process each
entry.
Ben
------------------------------
Date: Sun, 5 Sep 2010 00:39:02 +0200
From: Tuxedo <tuxedo@mailinator.com>
Subject: Re: Ideal data structure for nested list format?
Message-Id: <i5uhq6$mr5$03$1@news.t-online.com>
Ben Morrow wrote:
[...]
Many thanks for the detailed concept in how to build the particular menu
and list format. I understand it's not entirely ready-to-run code, and so
I'd like to know how your example can generate the final html code. Perhaps
you or someone here can help fill in the missing parts?:
#!/usr/bin/perl -w
use warnings;
use strict;
my @pages = (
{ page => "1.1.html", title => "Level 1.1", children => [
{ page => "2.1.html", title => "Level 2.1" },
{ page => "2.2.html", title => "Level 2.2", children => [
{ page => "3.1.html", title => "Level 3.1" },
{ page => "3.2.html", title => "Level 3.2" },
] },
{ page => "2.3.html", title => "Level 2.3" },
] },
);
# and then build a hash of 'parents', like so
sub populate_parents;
sub populate_parents {
my ($parents, $pages, $parent) = @_;
for (@$pages) {
my $page = $_->{page};
push @{$parents->{$page}}, $parent;
my $kids = $_->{children};
$kids and populate_parents $parents, @$kids, $page;
}
}
my %parents;
populate_parents \%parents, \@pages, undef;
# This will give you a data structure like
%parents = (
"1.1.html" => [undef],
"2.1.html" => [undef, "1.1.html"],
"3.1.html" => [undef, "1.1.html", "2.2.html"],
# ...
);
# Then, given a page name, you can build another hash
my $page = "3.1.html";
my $parents = $parents{$page};
my %class =
map +($parents->[$_] => "parent_level_$_"),
grep defined $parents->[$_],
0..$#$parents;
The above code 'as is' returns the error "Not an ARRAY reference at
./menu.pl line 23", which is on the line beginning with "for (@$pages) ".
If only the arrays and hashes could be generated without error, I can then
try to access and print the entries through some kind of loop construct.
Any additional ideas and code bits would be greatly appreciated!
Thanks again,
Tuxedo
------------------------------
Date: Sat, 04 Sep 2010 18:44:06 -0400
From: "Uri Guttman" <uri@StemSystems.com>
Subject: Re: Ideal data structure for nested list format?
Message-Id: <8739tpm8nd.fsf@quad.sysarch.com>
>>>>> "T" == Tuxedo <tuxedo@mailinator.com> writes:
T> Ben Morrow wrote:
T> [...]
T> Many thanks for the detailed concept in how to build the particular menu
T> and list format. I understand it's not entirely ready-to-run code, and so
T> I'd like to know how your example can generate the final html code. Perhaps
T> you or someone here can help fill in the missing parts?:
T> #!/usr/bin/perl -w
T> use warnings;
T> use strict;
T> my @pages = (
T> { page => "1.1.html", title => "Level 1.1", children => [
T> { page => "2.1.html", title => "Level 2.1" },
T> { page => "2.2.html", title => "Level 2.2", children => [
T> { page => "3.1.html", title => "Level 3.1" },
T> { page => "3.2.html", title => "Level 3.2" },
T> ] },
T> { page => "2.3.html", title => "Level 2.3" },
T> ] },
T> );
gack!! use a templater. many to choose from. check out mine called
Template::Simple. you pass it a data structure and template and you get
rendered text. nothing more to it. you can nest structures, templates
and template chunks all you want. lists are automatic too with no extra
markup (a list of elements renders a list of template chunks). all you
need to do is create your html templates (again, they can be included
and nested) and render with one call.
uri
--
Uri Guttman ------ uri@stemsystems.com -------- http://www.sysarch.com --
----- Perl Code Review , Architecture, Development, Training, Support ------
--------- Gourmet Hot Cocoa Mix ---- http://bestfriendscocoa.com ---------
------------------------------
Date: Sun, 5 Sep 2010 01:45:29 +0200
From: Tuxedo <tuxedo@mailinator.com>
Subject: Re: Ideal data structure for nested list format?
Message-Id: <i5ulmp$gcg$02$1@news.t-online.com>
Uri Guttman wrote:
[...]
> gack!! use a templater. many to choose from. check out mine called
> Template::Simple. you pass it a data structure and template and you get
> rendered text. nothing more to it. you can nest structures, templates
> and template chunks all you want. lists are automatic too with no extra
> markup (a list of elements renders a list of template chunks). all you
> need to do is create your html templates (again, they can be included
> and nested) and render with one call.
>
> uri
>
Thanks for the tip, I've not tried Template::Simple before so I'm not sure
how it works yet. I need to install and test it as well as delve into the
manual, which looks a little less than simple at first sight...
Can anyone advise me how to generate the following type of nested list by
Template::Simple?
<ul>
<li><a href=1.1.html>Level 1.1</a>
<ul>
<li><a href=2.1.html>Level 2.1</a></li>
<li><a href=2.2.html>Level 2.2</a>
<ul>
<li><a href=3.1.html>Level 3.1</a></li>
<li><a href=3.2.html>Level 3.2</a></li>
</ul>
</li>
<li><a href=2.3.html>Level 2.3</a></li>
</ul>
</li>
</ul>
And is it actually possible to apply the advanced formatting relating to
the $current_page URL along with any parent <li class=bits> if and where
parent entry <li>'s are present? (as detailed in my first post in this
thread). Can all of this be done with the help of Template::Simple?
Many thanks,
Tuxedo
------------------------------
Date: Sun, 5 Sep 2010 02:02:28 +0100
From: Ben Morrow <ben@morrow.me.uk>
Subject: Re: Ideal data structure for nested list format?
Message-Id: <4q6bl7-hmm.ln1@osiris.mauzo.dyndns.org>
Quoth Tuxedo <tuxedo@mailinator.com>:
> Ben Morrow wrote:
>
> Many thanks for the detailed concept in how to build the particular menu
> and list format. I understand it's not entirely ready-to-run code, and so
> I'd like to know how your example can generate the final html code. Perhaps
> you or someone here can help fill in the missing parts?:
>
<snip>
>
> The above code 'as is' returns the error "Not an ARRAY reference at
> ./menu.pl line 23", which is on the line beginning with "for (@$pages) ".
That would be because I'm an idiot, and was typing in the code without
testing it, and made an elementary mistake. However, I'm going to leave
it to you to find it, because you need to understand the code at least
that well before you use it. (I'll give you a hint: $pages isn't an
array reference, and it ought to be.)
Ben
------------------------------
Date: Sat, 04 Sep 2010 13:12:01 -0500
From: Tad McClellan <tadmc@seesig.invalid>
Subject: Re: Multidimensional array
Message-Id: <slrni852hu.a22.tadmc@tadbox.sbcglobal.net>
Paul E. Schoen <paul@pstech-inc.com> wrote:
> "Tad McClellan" <tadmc@seesig.invalid> wrote in message
> news:slrni832t7.7n3.tadmc@tadbox.sbcglobal.net...
>> Paul E. Schoen <paul@pstech-inc.com> wrote:
>>
>>> I'm not intentionally ignoring your advice, but I am trying to achieve a
>>> working level of proficiency and understanding,
>>
>> Replace the 2 lines that I showed you, and your working program
>> (with the hokey library) should continue to work (with CGI.pm).
>
> I did that, and it works very well.
Most excellent!
> But I
> didn't realize that the CGI package had the same function as the code in my
> script for handling the vars.
My followup was meant to point out that the CGI package had the same
function as the code in your script for handling the vars.
I guess I didn't say it very well.
>>> Today I tried using command
>>> line parameters
>> With CGI.pm you would test it from the command line thus:
>>
>> someprog name=Paul email='paul@pstech-inc.com'
^ ^
^ ^
Some shell quoting there. Waddya know?
>> Simple!
>
> I was able to get that to work on my local machine, but there is a Full_Name
> variable that has spaces in it, and I did not find any way to use it in
> command line parameters.
That is a problem with your lack of understanding of your very
own shell, not a Perl or CGI.pm problem.
Simply learn how to quote command line arguments in whatever shell
you are using.
Full_Name="Paul Schoen"
or even:
"Full_Name=Paul Schoen"
>> The code you showed some time ago was vulnerable to a Denial Of
>> Service attack. Have you mitigated that one somehow?
>
> I'm not sure how it is vulnerable to a DOS attack, or if that is likely to
> occur. This form will be accessed by only a few Sierra Club members,
So it is on some sort of internal network rather that the
World Wide Web then?
It if it accessable on the WWW, then you do not really know
who will be accessing it.
It can be accessed by pretty much anybody in the World. :-)
> and the
> correct Full_Name must be provided in order to proceed. Otherwise it returns
> "Unauthorized User". If the correct name is given, then the event
> information is verified for reasonable values (in the Submission Form's
> JavaScript),
You must validate it *again* on the server.
It is trivally easy to circumvent browser-side (Javascript) validation.
> before it will make the HTTP request to the CGI script.
It may not be a browser that is making the HTTP request.
Pretty much any program can make an HTTP request, programs known
as "browsers" are examples of only one such program.
> Of course anyone could look at the HTML source and find the URL of the perl
> script so it could be accessed from another site.
And if they call that Perl program 10,000 times a second, what happens?
Your server gets so slow at to be unusable.
Voila! You have been Denied the Service of that web server.
> Perhaps the perl script
> with the passwords in the cgi-bin could be examined and exploited in some
> way, but it would just send emails to me
at a rate of 10,000 times a second...
> I am concerned about security and I'd like to know if this is really likely
> to be subject to a malicious and debilitating attack,
If it is accessable on the WWW, then absolutely yes!
> Now I have been working on the HTML submission form and JavaScript to make
> sure the data is reasonable.
You must also make sure the data is reasonable by checking
it again *on the server*.
> I appreciate the help, and I understand your frustration with my bumbling
> attempts at getting this working.
You hang in there and we'll hang in there.
It ain't rocket science, (it's about one degree less complicated though :-)
--
Tad McClellan
email: perl -le "print scalar reverse qq/moc.liamg\100cm.j.dat/"
The above message is a Usenet post.
I don't recall having given anyone permission to use it on a Web site.
------------------------------
Date: Sat, 4 Sep 2010 17:36:23 -0400
From: "Paul E. Schoen" <paul@pstech-inc.com>
Subject: Re: Multidimensional array
Message-Id: <xZygo.49130$6o7.4042@newsfe21.iad>
"Tad McClellan" <tadmc@seesig.invalid> wrote in message
news:slrni852hu.a22.tadmc@tadbox.sbcglobal.net...
> Paul E. Schoen <paul@pstech-inc.com> wrote:
>>>> Today I tried using command
>>>> line parameters
>
>>> With CGI.pm you would test it from the command line thus:
>>>
>>> someprog name=Paul email='paul@pstech-inc.com'
> ^ ^
> ^ ^
>
> Some shell quoting there. Waddya know?
>
>
>> I was able to get that to work on my local machine, but there is a
>> Full_Name
>> variable that has spaces in it, and I did not find any way to use it in
>> command line parameters.
>
>
> That is a problem with your lack of understanding of your very
> own shell, not a Perl or CGI.pm problem.
>
> Simply learn how to quote command line arguments in whatever shell
> you are using.
>
>
> Full_Name="Paul Schoen"
> or even:
> "Full_Name=Paul Schoen"
These produced an error of "List form of pipe not implemented Line 42.
Using single quotes 'Paul Schoen' causes the script to reply
Unauthorized user: 'Paul
>> I'm not sure how it is vulnerable to a DOS attack, or if that is likely
>> to
>> occur. This form will be accessed by only a few Sierra Club members,
>
>
> So it is on some sort of internal network rather that the
> World Wide Web then?
>
> It if it accessable on the WWW, then you do not really know
> who will be accessing it.
>
> It can be accessed by pretty much anybody in the World. :-)
This is set up as a www application, but it is intended for only authorized
users.
>> and the
>> correct Full_Name must be provided in order to proceed. Otherwise it
>> returns
>> "Unauthorized User". If the correct name is given, then the event
>> information is verified for reasonable values (in the Submission Form's
>> JavaScript),
>
>
> You must validate it *again* on the server.
>
> It is trivally easy to circumvent browser-side (Javascript) validation.
Yes. The browser side validation is only to assure consistent entry of data
by the user.
>> before it will make the HTTP request to the CGI script.
>
> It may not be a browser that is making the HTTP request.
>
> Pretty much any program can make an HTTP request, programs known
> as "browsers" are examples of only one such program.
OK. I meant "in normal use".
>> Of course anyone could look at the HTML source and find the URL of the
>> perl
>> script so it could be accessed from another site.
> And if they call that Perl program 10,000 times a second, what happens?
>
> Your server gets so slow at to be unusable.
>
> Voila! You have been Denied the Service of that web server.
I had put a sleep(nSec) line in the perl script at one time. I did that so
the script would delay from the time it created or connected to the database
file before trying to access the table. Perhaps I could use that to limit
the rate at which the program would respond to HTTP requests. And I could
also set a variable at the start of the script which would bounce any
additional requests until the first has finished processing. Would that
work? I haven't read much of the documentation about security issues. Yet.
>> Perhaps the perl script
>> with the passwords in the cgi-bin could be examined and exploited in some
>> way, but it would just send emails to me
>
> at a rate of 10,000 times a second...
With the sleep() and the ignore request system this could be made
manageable, and perhaps the script can identify multiple requests from the
same source and blacklist it. But again, I need to read (and understand) the
documentation.
Also, perhaps I can make the directory where the HTML form is located
accessible only with a password. That will make it harder for a hacker to
see the HTML and the URL for the CGI script. I can also rename the Perl
script to a random string of characters, and abandon the one I'm now using
(which has been exposed already on this NG).
>> I am concerned about security and I'd like to know if this is really
>> likely
>> to be subject to a malicious and debilitating attack,
>
> If it is accessable on the WWW, then absolutely yes!
>
>
>> Now I have been working on the HTML submission form and JavaScript to
>> make
>> sure the data is reasonable.
>
>
> You must also make sure the data is reasonable by checking
> it again *on the server*.
Absolutely. The JavaScript is just for the legitimate user.
>> I appreciate the help, and I understand your frustration with my bumbling
>> attempts at getting this working.
>
> You hang in there and we'll hang in there.
>
> It ain't rocket science, (it's about one degree less complicated though
> :-)
There is a lot to learn, and the Perl language is just difficult for me to
grok. That's why I have used lots of comments in my script that seem
superfluous to those who are well versed in the language. I've only been
seriously coding in Perl for a little less than two weeks, and much of that
time was spent on problems with the server setup and basic understanding of
server side scripting and issues such as non-unix newlines.
I'm doing this project as a volunteer, and it would probably be enough for
me to simply receive emails from our members and then just format the
information in HTML and upload it to the server, without using CGI at all. I
could make a local script that would save me the work of formatting the HTML
using a text editor or an HTML optimized editor such as OpenOffice. The
former takes more time but the HTML is easier to read. The latter is fast
and gives quick WYSIWYG, but the HTML is horrible and bloated.
I think I'm close to being able to make this "live". Thanks.
Paul
------------------------------
Date: Sat, 04 Sep 2010 16:14:01 -0600
From: Scott Bryce <sbryce@scottbryce.com>
Subject: Re: Multidimensional array
Message-Id: <i5ugbi$ddd$1@news.eternal-september.org>
On 9/4/2010 3:36 PM, Paul E. Schoen wrote:
>> Full_Name="Paul Schoen"
>> or even:
>> "Full_Name=Paul Schoen"
>
> These produced an error of "List form of pipe not implemented Line 42.
>
> Using single quotes 'Paul Schoen' causes the script to reply
>
> Unauthorized user: 'Paul
What happens if you use:
Full_Name=Paul%20Schoen
------------------------------
Date: Sat, 04 Sep 2010 18:21:46 -0400
From: "Uri Guttman" <uri@StemSystems.com>
Subject: Re: Multidimensional array
Message-Id: <877hj1m9ol.fsf@quad.sysarch.com>
>>>>> "PES" == Paul E Schoen <paul@pstech-inc.com> writes:
>> That is a problem with your lack of understanding of your very
>> own shell, not a Perl or CGI.pm problem.
>>
>> Simply learn how to quote command line arguments in whatever shell
>> you are using.
>>
>>
>> Full_Name="Paul Schoen"
>> or even:
>> "Full_Name=Paul Schoen"
PES> These produced an error of "List form of pipe not implemented Line 42.
PES> Using single quotes 'Paul Schoen' causes the script to reply
PES> Unauthorized user: 'Paul
learn some shell stuff too. single quotes don't to ANYTHING on winblows
shells. unix shells allow both single or double quotes. did you actually
try the double quoted first version? it should work fine on
winblows. the second form is suspect IMO but i am not sure.
uri
--
Uri Guttman ------ uri@stemsystems.com -------- http://www.sysarch.com --
----- Perl Code Review , Architecture, Development, Training, Support ------
--------- Gourmet Hot Cocoa Mix ---- http://bestfriendscocoa.com ---------
------------------------------
Date: Sat, 4 Sep 2010 19:57:23 -0400
From: "Paul E. Schoen" <paul@pstech-inc.com>
Subject: Re: Multidimensional array
Message-Id: <J1Bgo.68331$wJ1.6213@newsfe08.iad>
"Scott Bryce" <sbryce@scottbryce.com> wrote in message
news:i5ugbi$ddd$1@news.eternal-september.org...
> On 9/4/2010 3:36 PM, Paul E. Schoen wrote:
>>> Full_Name="Paul Schoen"
>>> or even:
>>> "Full_Name=Paul Schoen"
>>
>> These produced an error of "List form of pipe not implemented Line 42.
>>
>> Using single quotes 'Paul Schoen' causes the script to reply
>>
>> Unauthorized user: 'Paul
>
> What happens if you use:
>
> Full_Name=Paul%20Schoen
List form of pipe not implemented.
I had tried that before with similar results. I'm using the command line in
Windoes Vista Business.
"Thanks for playing" :)
Paul
------------------------------
Date: 6 Apr 2001 21:33:47 GMT (Last modified)
From: Perl-Users-Request@ruby.oce.orst.edu (Perl-Users-Digest Admin)
Subject: Digest Administrivia (Last modified: 6 Apr 01)
Message-Id: <null>
Administrivia:
To submit articles to comp.lang.perl.announce, send your article to
clpa@perl.com.
Back issues are available via anonymous ftp from
ftp://cil-www.oce.orst.edu/pub/perl/old-digests.
#For other requests pertaining to the digest, send mail to
#perl-users-request@ruby.oce.orst.edu. Do not waste your time or mine
#sending perl questions to the -request address, I don't have time to
#answer them even if I did know the answer.
------------------------------
End of Perl-Users Digest V11 Issue 3116
***************************************
