[12030] in Perl-Users-Digest
Perl-Users Digest, Issue: 5630 Volume: 8
daemon@ATHENA.MIT.EDU (Perl-Users Digest)
Tue May 11 15:07:17 1999
Date: Tue, 11 May 99 12:00:16 -0700
From: Perl-Users Digest <Perl-Users-Request@ruby.OCE.ORST.EDU>
To: Perl-Users@ruby.OCE.ORST.EDU (Perl-Users Digest)
Perl-Users Digest Tue, 11 May 1999 Volume: 8 Number: 5630
Today's topics:
Adding a header with MIME::Entity <rfritz@pasco.k12.fl.us>
Learning Perl - help, please ! <carol@herb4.freeserve.co.uk>
Re: Learning Perl - help, please ! (Randal L. Schwartz)
Perl novice needs help <heinens@ghsp.com>
Re: tcgrep not expanding command-line wildcards (Eric Pement)
Re: Ten Tips toward *DIVERSITY COMPLIANCE* in Web Desig <flavell@mail.cern.ch>
Re: Ten Tips toward *DIVERSITY COMPLIANCE* in Web Desig (Charles R. Thompson)
Re: Ten Tips toward *DIVERSITY COMPLIANCE* in Web Desig <propart@mediaone.net>
Re: Ten Tips toward *DIVERSITY COMPLIANCE* in Web Desig (Larry Rosler)
Re: Ten Tips toward *DIVERSITY COMPLIANCE* in Web Desig (Chris Nandor)
Re: Ten Tips toward *DIVERSITY COMPLIANCE* in Web Desig (Charles R. Thompson)
Re: Ten Tips toward *DIVERSITY COMPLIANCE* in Web Desig (Randal L. Schwartz)
Re: Ten Tips toward *DIVERSITY COMPLIANCE* in Web Desig (Chris Nandor)
Re: Ten Tips toward *DIVERSITY COMPLIANCE* in Web Desig <juex@my-dejanews.com>
Re: This code just wont run. Any ideas? (Michel Dalle)
Re: This code just wont run. Any ideas? (Larry Rosler)
Re: This code just wont run. Any ideas? <rliu2@ford.com>
Re: Universal interface <swarren@www.wwwdotorg.org>
Special: Digest Administrivia (Last modified: 12 Dec 98 (Perl-Users-Digest Admin)
----------------------------------------------------------------------
Date: Tue, 11 May 1999 13:05:14 -0400
From: Richard Fritz <rfritz@pasco.k12.fl.us>
Subject: Adding a header with MIME::Entity
Message-Id: <3738634A.810CC216@pasco.k12.fl.us>
How can I add a header field to a message _after_ I have built it
like so?
my $mesg= MIME::Entity->build(
From=> "$school",
To=> "$servicegroup",
Subject=> "$subject",
Data=> @message );
Befpre sending, I want to be able to add a CC field to the structure;
but it needs to be optional, as it will not be necessary everytime.
TIA
------------------------------------------------------------------------
Richard Fritz, Systems Analyst (+ MLS) 813.794.2344 .2114(fax)
District School Board of Pasco County rfritz@pasco.k12.fl.us
------------------------------------------------------------------------
------------------------------
Date: Tue, 11 May 1999 19:17:23 +0100
From: "Carol Herbert" <carol@herb4.freeserve.co.uk>
Subject: Learning Perl - help, please !
Message-Id: <7h9sbp$b5e$1@news7.svr.pol.co.uk>
Sorry to be an idiot !
I am just beginning the Learning Perl book from O'Reilly - and it hasn't
taken long to come up against a problem :(
I have done the exercises at the end of chapter 3 - the one involving
inputting strings and getting them to print in reverse order and a random
selected word, put they do not work when tried through MSDos.
I have checked my script, which is exactly as it should be, and even tried
running the sample scripts ftp'd from the O'Reilly site - but their's don't
work either. Inputting is ok, but nothing is being printed.
I am ending the input of the string with ctrl+z (as recommended) - should I
be ending with something else ?
I am running Active Perl on an IBM pc running Windows 95. I know the Perl
is working as other scripts work ok.
Any help would be much appreciated.
carol@herb4.freeserve.co.uk
------------------------------
Date: 11 May 1999 11:40:05 -0700
From: merlyn@stonehenge.com (Randal L. Schwartz)
Subject: Re: Learning Perl - help, please !
Message-Id: <m1675zlabe.fsf@halfdome.holdit.com>
>>>>> "Carol" == Carol Herbert <carol@herb4.freeserve.co.uk> writes:
Carol> Sorry to be an idiot !
Carol> I am just beginning the Learning Perl book from O'Reilly - and it hasn't
Carol> taken long to come up against a problem :(
Carol> I have done the exercises at the end of chapter 3 - the one
Carol> involving inputting strings and getting them to print in
Carol> reverse order and a random selected word, put they do not work
Carol> when tried through MSDos.
If you are using DOS, you should have gotten "Learning Perl for Win32
Systems" instead, which has been translated from the original native
Unix tongue to that foreign Redmond-speak.
Sorry, I can't tell you what's different. I wrote the parts that are
the same, not the parts that are different. :)
print "Just another Perl hacker,"
--
Name: Randal L. Schwartz / Stonehenge Consulting Services (503)777-0095
Keywords: Perl training, UNIX[tm] consulting, video production, skiing, flying
Email: <merlyn@stonehenge.com> Snail: (Call) PGP-Key: (finger merlyn@teleport.com)
Web: <A HREF="http://www.stonehenge.com/merlyn/">My Home Page!</A>
Quote: "I'm telling you, if I could have five lines in my .sig, I would!" -- me
------------------------------
Date: 11 May 1999 18:20:15 GMT
From: "Scott Heinen" <heinens@ghsp.com>
Subject: Perl novice needs help
Message-Id: <7h9scv$4um$0@205.138.138.3>
Hello all. I just started working with perl yesterday. Basically what my
goal is is this: let a person search a list via a form in a web browser. I
have a list of data, each entry separated by tabs, and I would be searching
by 2 possible criteria, one or the other, not both. I can make a table in
html, thats easy, and I have the meat of the script done. My problem comes
when I have to write that part that takes the info from the html table and
uses it on the search process and then returns the results to a form
viewable in the web browser. Here is my code:
#!/usr/bin/perl -w
# The name of the database file
$TheDB = "printerlist.txt";
# Open the database file but quit if it does not exist
open(INDB, $TheDB) or die "The database $TheDB could " .
"not be found.\n";
while(1) { # Loop forever
print "\nDo you want to search by employee IP Address (I), \n" .
" Printer Name(P), or quit (Q): ";
$DoSearch = <STDIN>;
chomp($DoSearch);
$DoSearch =~ tr/A-Z/a-z/;
# Check if they want to quit
if ($DoSearch eq 'q') { last }
# Check if they did *not* say i or I
if ($DoSearch ne 'i') {
if ($DoSearch ne 'p') {
print "You must enter either I, P, or Q.\n";
next; # Go out to the while loop
}
}
if ($DoSearch eq 'i') {
#Ask them what IP Address they want to search for
print "Search for IP address: ";
$SearchFor = <STDIN>;
chomp($SearchFor);
# Go to the top of the database in cast this isn't
# the first time they are searching
seek(INDB, 0, 0);
# Reset the count of successes
$SuccessCount = 0;
# Loop through the records in the file
while(<INDB>) {
$TheRec = $_;
chomp($TheRec);
($PrinterName, $Location, $Model, $IPAddress, $HardwareAddress,
$JetdirectModel) =
split(/\t/, $TheRec);
if($IPAddress eq $SearchFor) {
$SuccessCount = $SuccessCount + 1;
print "\nIP Address: $IPAddress\n";
print "Printer Name: $PrinterName\n";
print "Location: $Location\n";
print "Model: $Model\n";
print "Hardware Address: $HardwareAddress\n";
print "JetDirect Model: $JetdirectModel\n \n";
} # End of if
} # End of while (<INDB>)
if ($SuccessCount == 0) { print "No records found.\n" }
else { print "$SuccessCount records found.\n" }
}
if ($DoSearch eq 'p') {
#Ask them what Printer Name they want to search for
print "Search for Printer Name(case sensitive!): ";
$SearchFor = <STDIN>;
chomp($SearchFor);
# Go to the top of the database in cast this isn't
# the first time they are searching
seek(INDB, 0, 0);
# Reset the count of successes
$SuccessCount = 0;
# Loop through the records in the file
while(<INDB>) {
$TheRec = $_;
chomp($TheRec);
($PrinterName, $Location, $Model, $IPAddress, $HardwareAddress,
$JetdirectModel) =
split(/\t/, $TheRec);
if($PrinterName eq $SearchFor) {
$SuccessCount = $SuccessCount + 1;
print "\nIP Address: $IPAddress\n";
print "Printer Name: $PrinterName\n";
print "Location: $Location\n";
print "Model: $Model\n";
print "Hardware Address: $HardwareAddress\n";
print "JetDirect Model: $JetdirectModel\n \n";
} # End of if
} # End of while (<INDB>)
if ($SuccessCount == 0) { print "No records found.\n" }
else { print "$SuccessCount records found.\n" }
}
} # End of while(1)
print "Program finished.\n";
If this script looks familiar its because much of it came from Perl for
Dummies, but it was perfect for my application up to this point. Whether or
not it will work with the form processing is not something I am able to
decide. If anyone can help me with the code I need to add though, I would
really appreciate it. Also if there are any questions as to what I am doing,
please let me know. I would prefer to work on this via email, but I
understand that might not be convenient for some people. Thanks either way!!
Me
------------------------------
Date: Tue, 11 May 1999 18:21:23 GMT
From: epement@jpusa.chi.il.us (Eric Pement)
Subject: Re: tcgrep not expanding command-line wildcards
Message-Id: <37387019.72254394@news.jpusa.net>
On 9 May 1999 01:55:43 GMT, bbirthisel@aol.com (Bbirthisel) wrote in
reply to my message (marked in double arrows, >>):
>> Thanks for letting me know about this. I was surprised to think that
>>any version of Perl running on a Win32 system WOULDN'T automatically
>>support ambiguous filespecs (or "filename globbing" as they say now).
>>Given that the installation program knows its running under Windows, and
>>not under (say) bash or tcsh, I would think it ought to add the glob
>>expansion automatically.
>
>Actually, quite a few Windows users run under replacement shells
>including bash and 4DOS. The default braindead versions aren't
>even compatible with each other between all Windows varients.
>You end up with real "ambiguous filespecs" instead of "wildcard
>file selection".
Yes, but there is such a thing as a "most likely" conjecture when
installing software.
I would check first for the existence of a CONFIG.SYS file. If found,
check for the existence of a "SHELL=" line. If CONFIG.SYS is not found
or if the "SHELL=" line reads COMMAND.COM, 4DOS.COM, TCMD.COM, DR-DOS,
or some other command shell which is known _not_ to expand wildcards for
external programs, then the Perl file globbing routines should be added
automatically. (I suspect this would accommodate over 90 percent of the
installations of Perl on Win9+ machines.) If the SHELL= line points to
an unknown command interpreter, then the file globbing routines could be
omitted. Just a thought of trying to improve the installation.
--
Eric Pement <epement@jpusa.org>
senior editor, Cornerstone magazine
http://www.cornerstonemag.com
939 W. Wilson, Chicago, IL 60640
tel: 773/561-2450, 1-(ext.)2084 fax: 773/989-2076
------------------------------
Date: Tue, 11 May 1999 19:46:45 +0200
From: "Alan J. Flavell" <flavell@mail.cern.ch>
Subject: Re: Ten Tips toward *DIVERSITY COMPLIANCE* in Web Design
Message-Id: <Pine.HPP.3.95a.990511192303.23884B-100000@hpplus01.cern.ch>
With respect, Sir, your rant, which I substantially support, was
way off topic for this group. F'ups set.
On 11 May 1999, Tom Christiansen wrote:
> It is extremely important that all information be maximally accessible
> to everyone, even people who use systems different than your own.
You'll find a lot of disagreement on this. The key points, to my way
of thinking, are:
- the most important individual visitors to a site are the indexing
robots
- a "target audience" is categorised by its interest in the topic
of your web pages; generally that implies nothing about their
current browsing environment. Someone interested in virtual
reality might still want to check some facts on their cellphone
browser, to take just one example from many.
> 3) All <IMG> tags must have useful ALT-text, and be navigable even
> without pictures.
Good, but in some cases the "useful" ALT text is ALT=""
By the way, have you tried to use the newly-designed dejanews
from Lynx; it's an unmitigated disaster. And just after the WAI
guidelines have been finalised, gorblimey.
> 5) Make sure the HTML validates. W3C has several validators, including
> weblint -pedantic and more.
It's a pity that the term "validator" isn't reserved for its strict
SGML-context meaning, and the terms "checker" or "linter" used for these
other functions.
> 7) There must be no moving pictures or pop-ups, *ever*, even if someone
> wants to personally pay ten grand for it.
But these can form illustrations in ways that are simply without
comparison. While I agree with you that it is a bad idea to scatter
them around as mere decoration, it's a case of throwing out the baby
with the bathwater that you are ordering people never to use them.
This isn't going to work: the WWW cannot be made safe by you and I
agreeing to give up animations. Someone who's browsing the WWW at risk
of a seizure needs to protect themselves with appropriate software,
e.g a browser that can disable gif animations. There's nothing that you
and I can do on our own initiative as authors that's going to change
that situation, frankly, and it would be a great pity to give up a
technique that carries useful functionality when used purposefully, on
the grounds that it has been widely abused.
I'm sorry, I think you weakened your case (which is otherwise a good
one, and I'm sure well-motivated) with a number of points of
exaggeration.
Are you going to put this on a web page? ;-)
------------------------------
Date: Tue, 11 May 1999 18:13:19 GMT
From: design@raincloud-studios.com (Charles R. Thompson)
Subject: Re: Ten Tips toward *DIVERSITY COMPLIANCE* in Web Design
Message-Id: <MPG.11a23e88da659fab989694@news>
[This followup was posted to comp.lang.perl.misc and a copy was sent to
the cited author.]
In article <37385820@cs.colorado.edu>, Tom Christiansen says...
> It is extremely important that all information be maximally accessible
^^^^^^^^^^^
> to everyone, even people who use systems different than your own.
> If the choice ever comes down to making something should look nice for
> some people at the expense of being virtually unusable to others, you
> *must* choose the more humdrum look. This is about information sharing,
^^^^^^^^^^^^^^^^^^^
> ladies and gentlemen, not about holding someone prisoner.
Although I have addressed other areas here in another message, everyone
has failed to point out the obvious.
I think it's perfectly valid to say these guidelines should *clearly*
apply to _information_ based sites. The commercial applications for the
Web have taken on a non-stoppable life of their own and could never be
governed by such rules. Period. It's a losing battle in that arena.
It's always nice to find a commercial site by someone making a valid
attempt at compatibility... hey.. it's not that easy to do, but again...
information and commercialism are two different concepts that I find are
extremely difficult to govern by the same rules.
Perl isn't stamped on a patch of the pants worn by semi-anorexic Teeny
Boppers with bad attitudes and matching funky hair. Therefore, you don't
need Flash, ActiveX, color or Java(Script) to illustrate a Perl code
concept. Perl's code and merits are their own 'hype machines.'
--
Charles R. Thompson
RainCloud Studios
"That? That's no script. That's your attempt at a rather complex README
file."
------------------------------
Date: Tue, 11 May 1999 14:13:34 -0400
From: PropART <propart@mediaone.net>
Subject: Re: Ten Tips toward *DIVERSITY COMPLIANCE* in Web Design
Message-Id: <3738734D.A631158B@mediaone.net>
Chris Nandor wrote:
> Anyway, HTML by definition does define what something will look like.
> Talking about defining presentation with HTML makes no sense. It's like
> talking about playing baseball with golf clubs.
Not to a designer's definition of what something will look like... What if guy 1
looks at your page at 640 x 480 and guy2 looks at it at 1024x768. That's why HTML
table's are often used for the purpose (illegitimate, by TC's credo) of
controlling presentation...
>
> DHTML does not exist as a "thing". It is a mostly meaningless word used
> to group together disparate technologies that people happen to use
> together for some reason or another.
OK... read CSS and CSS-P, and scripting to the DOM of a particular browser with
JavaScript for DHTML... Bascially, everything that's covered in the Flamingo
O'Reilly Book... TC retracted what he said about style sheets, but still implies
that you shouldn't use JavaScript or any animation technology...
-- William C.
------------------------------
Date: Tue, 11 May 1999 11:24:59 -0700
From: lr@hpl.hp.com (Larry Rosler)
Subject: Re: Ten Tips toward *DIVERSITY COMPLIANCE* in Web Design
Message-Id: <MPG.11a215d03fc7133e989a2c@nntp.hpl.hp.com>
[Posted and a courtesy copy mailed.]
In article <pudge-1105991349470001@192.168.0.77> on Tue, 11 May 1999
17:49:46 GMT, Chris Nandor <pudge@pobox.com> says...
...
> Anyway, HTML by definition does define what something will look like.
> Talking about defining presentation with HTML makes no sense. It's like
> talking about playing baseball with golf clubs.
>From your next post:
> It has nothing to do with HTML 2.0. Again, HTML, by definition, cannot
> define what something will look like, no matter what the version. HTML
> is a *device-independent* markup language.
I think a negative is missing in the first sentence quoted, and I'm
drawing it to your attention to avoid confusion among the readers.
--
(Just Another Larry) Rosler
Hewlett-Packard Company
http://www.hpl.hp.com/personal/Larry_Rosler/
lr@hpl.hp.com
------------------------------
Date: Tue, 11 May 1999 18:28:28 GMT
From: pudge@pobox.com (Chris Nandor)
Subject: Re: Ten Tips toward *DIVERSITY COMPLIANCE* in Web Design
Message-Id: <pudge-1105991428290001@192.168.0.77>
In article <MPG.11a215d03fc7133e989a2c@nntp.hpl.hp.com>, lr@hpl.hp.com
(Larry Rosler) wrote:
# [Posted and a courtesy copy mailed.]
#
# In article <pudge-1105991349470001@192.168.0.77> on Tue, 11 May 1999
# 17:49:46 GMT, Chris Nandor <pudge@pobox.com> says...
# ...
# > Anyway, HTML by definition does define what something will look like.
# > Talking about defining presentation with HTML makes no sense. It's like
# > talking about playing baseball with golf clubs.
#
# From your next post:
#
# > It has nothing to do with HTML 2.0. Again, HTML, by definition, cannot
# > define what something will look like, no matter what the version. HTML
# > is a *device-independent* markup language.
#
# I think a negative is missing in the first sentence quoted, and I'm
# drawing it to your attention to avoid confusion among the readers.
Thanks much, yes. HTML does NOT define what something will look like.
--
Chris Nandor mailto:pudge@pobox.com http://pudge.net/
%PGPKey = ('B76E72AD', [1024, '0824090B CE73CA10 1FF77F13 8180B6B6'])
------------------------------
Date: Tue, 11 May 1999 18:28:38 GMT
From: design@raincloud-studios.com (Charles R. Thompson)
Subject: Re: Ten Tips toward *DIVERSITY COMPLIANCE* in Web Design
Message-Id: <MPG.11a242351237d5fb989695@news>
[This followup was posted to comp.lang.perl.misc and a copy was sent to
the cited author.]
In article <3738734D.A631158B@mediaone.net>, PropART says...
> but still implies
> that you shouldn't use JavaScript or any animation technology...
I say Bully. IMO, JavaScript only has two valid uses which are
'workaroundable' anyway.
1) Form checking...
If you aren't checking it on the backend as well, your scripts are
vunerable to invalid direct URL attacks. It should only be used as a
'front end' immediate check to reduce the load on your server. If it's
valid from there, your script will have no problem quickly flipping
through it's checking routines.
2) Rollovers
Properly coded, JavaScript will be ignored by those not using it, and as
long as you use a valid 'unclicked state' this shouldn't even be an
issue.
3) Flash
It has conditional coding for using standard GIF images.
In general however... none of this crap belongs in a *true information
based capacity* anyway.
--
Charles R. Thompson
RainCloud Studios
"That? That's no script. That's your attempt at a rather complex README
file."
------------------------------
Date: 11 May 1999 11:28:37 -0700
From: merlyn@stonehenge.com (Randal L. Schwartz)
Subject: Re: Ten Tips toward *DIVERSITY COMPLIANCE* in Web Design
Message-Id: <m1btfrlaui.fsf@halfdome.holdit.com>
>>>>> "PropART" == PropART <propart@mediaone.net> writes:
PropART> Not to a designer's definition of what something will look
PropART> like... What if guy 1 looks at your page at 640 x 480 and
PropART> guy2 looks at it at 1024x768. That's why HTML table's are
PropART> often used for the purpose (illegitimate, by TC's credo) of
PropART> controlling presentation...
If I look at it on a terminal that's twice as wide (or half as wide),
I'd expect the table to refill the width available. Tables are fine,
used correctly.
But the real problem with this thread is that this has been hashed
over MANY MANY times by the folks in CIWAH. Please go read any number
of Dejanews hits on that group.
--
Name: Randal L. Schwartz / Stonehenge Consulting Services (503)777-0095
Keywords: Perl training, UNIX[tm] consulting, video production, skiing, flying
Email: <merlyn@stonehenge.com> Snail: (Call) PGP-Key: (finger merlyn@teleport.com)
Web: <A HREF="http://www.stonehenge.com/merlyn/">My Home Page!</A>
Quote: "I'm telling you, if I could have five lines in my .sig, I would!" -- me
------------------------------
Date: Tue, 11 May 1999 18:43:52 GMT
From: pudge@pobox.com (Chris Nandor)
Subject: Re: Ten Tips toward *DIVERSITY COMPLIANCE* in Web Design
Message-Id: <pudge-1105991443540001@192.168.0.77>
In article <3738734D.A631158B@mediaone.net>, PropART
<propart@mediaone.net> wrote:
# Chris Nandor wrote:
#
# > Anyway, HTML by definition does define what something will look like.
# > Talking about defining presentation with HTML makes no sense. It's like
# > talking about playing baseball with golf clubs.
#
# Not to a designer's definition of what something will look like... What
if guy
1
# looks at your page at 640 x 480 and guy2 looks at it at 1024x768. That's why
HTML
# table's are often used for the purpose (illegitimate, by TC's credo) of
# controlling presentation...
Please, again, fix your columns. You are breaking your lines at more than
the standard 80 columns.
Anyway, HTML DOES NOT DEFINE WHAT SOMETHING WILL LOOK LIKE. Period. HTML
does not even define that the contents will be viewed at all! Many people
listen to HTML, or read it in braille.
# > DHTML does not exist as a "thing". It is a mostly meaningless word used
# > to group together disparate technologies that people happen to use
# > together for some reason or another.
#
# OK... read CSS and CSS-P, and scripting to the DOM of a particular browser
with
# JavaScript for DHTML... Bascially, everything that's covered in the Flamingo
# O'Reilly Book...
I don't know what this "sentence" is trying to say. Could you rephrase
it? Are you saying DHTML is a thing? It isn't. I don't care what
O'Reilly says. DHTML is a non-entity. Each technology included in the
so-called DHTML is basically unrelated to the others. Of course, they can
be made to work together in some ways. But I can make it so I click on a
mail address in my text editor and it opens my mail program. That doesn't
mean that my text editor and mail program are part of some new thing.
They are two different, distinct, disparate technologies.
# TC retracted what he said about style sheets, but still
implies
# that you shouldn't use JavaScript or any animation technology...
Well, I do use JavaScript, but I make sure that it is optional and that
people who don't use it will not even notice it unless they choose to view
the source. This is the Right Way, if you are to use them. I use frames,
but as soon as I get some spare time I am going to get rid of them. I
haven't touched my site design in a long time.
Regardless, I am all for the use of proper HTML, but I am not as adamant
about not using extrahtml features within HTML, as long as they do not
detract from the use of the site by browsers that do not support those
features.
After all, when it comes down to using embedded QuickTime or Java, at some
point it is little more than serving multimedia via HTTP, and it has
little to do with HTML at all. So anything extrahtml needs to be really
extra. When I put multimedia content up, it is as a separate link,
usually. But the main principle is that it should not interfere in any
way with someone using lynx or braille readers, or whatever.
And again, don't use my site as a guideline. I've been too busy for the
past year to fix it. Although, in my own defense, it worked fine in lynx
until lynx added frame support! lynx is supposed to show what is in my
NOFRAMES tags, but instead it just shows a list of framesets to link to.
Unfortunate ... they chose to adjust for people who were NOT doing it
right and using NOFRAMES tags, so people who were using NOFRAMES tags get
screwed.
But that's another topic. :)
--
Chris Nandor mailto:pudge@pobox.com http://pudge.net/
%PGPKey = ('B76E72AD', [1024, '0824090B CE73CA10 1FF77F13 8180B6B6'])
------------------------------
Date: Tue, 11 May 1999 11:47:02 -0700
From: "J|rgen Exner" <juex@my-dejanews.com>
Subject: Re: Ten Tips toward *DIVERSITY COMPLIANCE* in Web Design
Message-Id: <7h9trb$l6j@news.dns.microsoft.com>
Tom Christiansen <tchrist@mox.perl.com> wrote in message
news:37385820@cs.colorado.edu...
[a lot of HTML stuff]
Somehow I fail to see the relation with Perl.
Do you mind to explain?
jue
--
J|rgen Exner
------------------------------
Date: Tue, 11 May 1999 18:03:02 GMT
From: michel.dalle@usa.net (Michel Dalle)
Subject: Re: This code just wont run. Any ideas?
Message-Id: <7h9rca$pc$1@news.mch.sbs.de>
In article <7h9qgv$h77$1@gxsn.com>, "Daniel Vesma" <daniel.vesma@thewebtree.com> wrote:
>Hi,
>
>This code for some reason doesn't want to run.
>
>I tried to get it down to as small as possible, but it still doesn't run...
>
Some questions :
- When you try perl -w, does it actually say "I don't want to run", or
does it say something else ? :-)
- Have you tried it via command line too ?
- What does the error logfile of your webserver say ?
Happy hunting,
Michel.
--
aWebVisit - extracts visitor information from WWW logfiles and shows
the top entry, transit, exit and 'hit&run' pages, the links followed
inside your website, the time spent per page, the visit duration etc.
For more details, see http://gallery.uunet.be/Michel.Dalle/awv.html
------------------------------
Date: Tue, 11 May 1999 11:38:52 -0700
From: lr@hpl.hp.com (Larry Rosler)
Subject: Re: This code just wont run. Any ideas?
Message-Id: <MPG.11a2191a6b9a4528989a2d@nntp.hpl.hp.com>
[Posted and a courtesy copy mailed.]
In article <7h9qgv$h77$1@gxsn.com> on Tue, 11 May 1999 18:49:13 +0100,
Daniel Vesma <daniel.vesma@thewebtree.com> says...
> This code for some reason doesn't want to run.
You haven't said what it does instead of running. Had you tested it
from the command line, at least one error would have been apparent.
Instead the error messages are probably in your server log.
> I tried to get it down to as small as possible, but it still doesn't run...
>
> #!/usr/bin/perl
Get into the habit of using the '-w' flag on this line. You will never
regret it! And get into the habit of using 'use strict;' as the first
source line. Declaring all your variables will take a tiny bit of
effort. You will never regret it!
> use CGI qw(param);
>
> print "Content-type: text/html\n\n";
>
> $ID = param("ID");
> $PASS = param("PASS");
> $body = param("body");
> $to = "daniel.vesma@thewebtree.com";
The line above is probably where the problem lies. You use double-
quotes on strings, even when you don't want variable interpolation or
backslash interpretation. The @ needs to be escaped in a double-quoted
string. Use single quotes (my choice) or put a backslash ahead of the
@.
> $sendmail = "/usr/sbin/sendmail";
> $sendmail_flags = "-oi -t";
>
> ######## I think this line is to blame ##########
> open(MAIL,"|$sendmail $sendmail_flags") || &Exit("Could not execute
> \"$sendmail\"");
Include the reason for the failure $! in the error message. Where does
the error message go?
<SNIP>
> print <<"END";
The double-quotes are the default, so you could leave them out.
>
> <HTML>
> <HEAD>
> <TITLE>private view 1.0</TITLE>
> </HEAD>
> <BODY">
?
--
(Just Another Larry) Rosler
Hewlett-Packard Company
http://www.hpl.hp.com/personal/Larry_Rosler/
lr@hpl.hp.com
------------------------------
Date: Tue, 11 May 1999 14:23:19 -0400
From: Roger Liu <rliu2@ford.com>
To: Daniel Vesma <daniel.vesma@thewebtree.com>
Subject: Re: This code just wont run. Any ideas?
Message-Id: <37387597.D41F2D6B@ford.com>
This is a multi-part message in MIME format.
--------------1E1D5E5B3E30BADAC2E8CFE0
Content-Type: text/plain; charset=us-ascii
Content-Transfer-Encoding: 7bit
> $to = "daniel.vesma@thewebtree.com";
^^^^^^^
Change @ to \@
Roger
--------------1E1D5E5B3E30BADAC2E8CFE0
Content-Type: text/x-vcard; charset=us-ascii;
name="rliu2.vcf"
Content-Transfer-Encoding: 7bit
Content-Description: Card for Roger Liu
Content-Disposition: attachment;
filename="rliu2.vcf"
begin:vcard
n:Liu;Roger
tel;fax:(313)322-3619
tel;home:(734)572-1634
tel;work:(313)248-3197
x-mozilla-html:FALSE
adr:;;;;;;
version:2.1
email;internet:rliu2@ford.com
title:Programmer/Analyst
fn:Roger Liu
end:vcard
--------------1E1D5E5B3E30BADAC2E8CFE0--
------------------------------
Date: Tue, 11 May 1999 18:54:24 GMT
From: "Stephen Warren" <swarren@www.wwwdotorg.org>
Subject: Re: Universal interface
Message-Id: <A1%Z2.220$6x6.108@news.rdc1.sfba.home.com>
Pavel Kotala <pkotala@logis.cz> wrote in message
news:926405368.36842@gate.logis.cz...
> We need to wirte some universal interface between several applications on
> various platforms (PC-Win, DOS, UNIX) running on various DB
> (X-BASE,text,ORACLE). Now we try to write some code in Perl.
>
> I wold like to ask.
> Is Perl secure platform (authorising-user and password,etc.)?
>
> I like programming in Perl (multiplatform TCP/IP,DB by a few code). But is
> decision to use Perl right? Or should we use any other language (eg.
java-I
> don4t know it-is programming multiplatform,multiDB so easy as in Perl?, On
> the other hand, we would like to have some executable secure format, not a
> script.).
Perl sounds like a perfectly good choice; It's pretty multi-platform, does
networking/DB stuff well.
Perl can be made as secure as any other language - it's 'just' a language!
The only possible point you raise is about easy source availability. You
could try giving execute-only (i.e. not read) permission to the scripts (I
think this works!). An interesting point is that Java is pretty easy to
decompile in many ways - a lot of the original symbols exist in the
byte-code, so reverse engineering it to source is not impossible. It's
certainly not worth relying on for security!
The best thing to do is to implement secure algorithms, so that no matter
what language you use, and no matter who has source, the system is still
secure. Not always easy!
--
Stephen Warren, Snr Systems Engineer, Technology House, San Francisco
mailto:swarren@techhouse.com http://www.techhouse.com/
mailto:swarren@wwwdotorg.org http://www.wwwdotorg.org/
MIME, S/MIME and HTML mail are acceptable
------------------------------
Date: 12 Dec 98 21:33:47 GMT (Last modified)
From: Perl-Request@ruby.oce.orst.edu (Perl-Users-Digest Admin)
Subject: Special: Digest Administrivia (Last modified: 12 Dec 98)
Message-Id: <null>
Administrivia:
Well, after 6 months, here's the answer to the quiz: what do we do about
comp.lang.perl.moderated. Answer: nothing.
]From: Russ Allbery <rra@stanford.edu>
]Date: 21 Sep 1998 19:53:43 -0700
]Subject: comp.lang.perl.moderated available via e-mail
]
]It is possible to subscribe to comp.lang.perl.moderated as a mailing list.
]To do so, send mail to majordomo@eyrie.org with "subscribe clpm" in the
]body. Majordomo will then send you instructions on how to confirm your
]subscription. This is provided as a general service for those people who
]cannot receive the newsgroup for whatever reason or who just prefer to
]receive messages via e-mail.
The Perl-Users Digest is a retransmission of the USENET newsgroup
comp.lang.perl.misc. For subscription or unsubscription requests, send
the single line:
subscribe perl-users
or:
unsubscribe perl-users
to almanac@ruby.oce.orst.edu.
To submit articles to comp.lang.perl.misc (and this Digest), send your
article to perl-users@ruby.oce.orst.edu.
To submit articles to comp.lang.perl.announce, send your article to
clpa@perl.com.
To request back copies (available for a week or so), send your request
to almanac@ruby.oce.orst.edu with the command "send perl-users x.y",
where x is the volume number and y is the issue number.
The Meta-FAQ, an article containing information about the FAQ, is
available by requesting "send perl-users meta-faq". The real FAQ, as it
appeared last in the newsgroup, can be retrieved with the request "send
perl-users FAQ". Due to their sizes, neither the Meta-FAQ nor the FAQ
are included in the digest.
The "mini-FAQ", which is an updated version of the Meta-FAQ, is
available by requesting "send perl-users mini-faq". It appears twice
weekly in the group, but is not distributed in the digest.
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 V8 Issue 5630
**************************************
