[29775] in Perl-Users-Digest
Perl-Users Digest, Issue: 1018 Volume: 11
daemon@ATHENA.MIT.EDU (Perl-Users Digest)
Fri Nov 9 09:09:41 2007
Date: Fri, 9 Nov 2007 06:09:05 -0800 (PST)
From: Perl-Users Digest <Perl-Users-Request@ruby.OCE.ORST.EDU>
To: Perl-Users@ruby.OCE.ORST.EDU (Perl-Users Digest)
Perl-Users Digest Fri, 9 Nov 2007 Volume: 11 Number: 1018
Today's topics:
file processing in Perl <jao16@hotmail.com>
Re: file processing in Perl <jurgenex@hotmail.com>
Re: file processing in Perl <ben@morrow.me.uk>
Re: file processing in Perl <mritty@gmail.com>
Re: file processing in Perl <krahnj@telus.net>
Re: make on TK fails on Solaris 10 <ben@morrow.me.uk>
Posting Guidelines for comp.lang.perl.misc ($Revision: tadmc@seesig.invalid
Re: script to make font as a grid in plain text? <myicq2@3gmx.net4>
Re: Set TCP_MAXSEG (OS buffering) on Win32? How? <ben@morrow.me.uk>
Re: SOAP server & client problem <RedGrittyBrick@SpamWeary.foo>
Re: SOAP server & client problem <waleed.harbi@gmail.com>
Re: Why can't you slice an array @a[3..-1]? <bik.mido@tiscalinet.it>
Re: Why can't you slice an array @a[3..-1]? <bik.mido@tiscalinet.it>
Re: Why can't you slice an array @a[3..-1]? <mritty@gmail.com>
Digest Administrivia (Last modified: 6 Apr 01) (Perl-Users-Digest Admin)
----------------------------------------------------------------------
Date: Fri, 09 Nov 2007 04:01:49 -0800
From: thunder <jao16@hotmail.com>
Subject: file processing in Perl
Message-Id: <1194609709.596399.311340@s15g2000prm.googlegroups.com>
Hello
I am trying to read a file in perl and then process it.
Each line of the file consists of a 32-bit hex value.
I am using
while ($input_line = <IN_FILE>) {
.....
}
However, for each line i read i want to interpret it as a data value
and do some shifting to this data value. But perl still thinks this
is a string value and won't allow me to do the shifting.
QS; How do i convert the string value of the line read to a scalar/
data value?
Any other suggestions greatly appreciated.
Thanks in advance
J
------------------------------
Date: Fri, 09 Nov 2007 12:49:14 GMT
From: "Jürgen Exner" <jurgenex@hotmail.com>
Subject: Re: file processing in Perl
Message-Id: <eHYYi.13016$%n.12601@trndny07>
thunder wrote:
> Each line of the file consists of a 32-bit hex value.
>
> However, for each line i read i want to interpret it as a data value
> and do some shifting to this data value. But perl still thinks this
> is a string value and won't allow me to do the shifting.
> QS; How do i convert the string value of the line read to a scalar/
> data value?
Well, but strings _are_ scalars as well as data.
Maybe you are looking for unpack()?
jue
------------------------------
Date: Fri, 9 Nov 2007 13:13:57 +0000
From: Ben Morrow <ben@morrow.me.uk>
Subject: Re: file processing in Perl
Message-Id: <l13e05-19c.ln1@osiris.mauzo.dyndns.org>
Quoth thunder <jao16@hotmail.com>:
>
> I am trying to read a file in perl and then process it.
>
> Each line of the file consists of a 32-bit hex value.
>
<snip>
> However, for each line i read i want to interpret it as a data value
You mean 'as a number'. You want unpack with the 'H' format.
Ben
------------------------------
Date: Fri, 09 Nov 2007 05:16:29 -0800
From: Paul Lalli <mritty@gmail.com>
Subject: Re: file processing in Perl
Message-Id: <1194614189.380499.244370@i38g2000prf.googlegroups.com>
On Nov 9, 7:01 am, thunder <ja...@hotmail.com> wrote:
> Each line of the file consists of a 32-bit hex value.
>
> I am using
>
> while ($input_line = <IN_FILE>) {
> .....
> }
>
> However, for each line i read i want to interpret it as a data
> value and do some shifting to this data value. But perl still
> thinks this is a string value and won't allow me to do the
> shifting.
>
> QS; How do i convert the string value of the line read to a scalar/
> data value?
Your question is nonsensical. A string IS a scalar, and IS data.
What is it you actually want to do? Provide sample input and desired
output to demonstrate.
Paul Lalli
------------------------------
Date: Fri, 09 Nov 2007 13:19:46 GMT
From: "John W. Krahn" <krahnj@telus.net>
Subject: Re: file processing in Perl
Message-Id: <47345E31.4505BA9F@telus.net>
thunder wrote:
>
> I am trying to read a file in perl and then process it.
>
> Each line of the file consists of a 32-bit hex value.
>
> I am using
>
> while ($input_line = <IN_FILE>) {
> .....
> }
>
> However, for each line i read i want to interpret it as a data value
> and do some shifting to this data value. But perl still thinks this
> is a string value and won't allow me to do the shifting.
$ perl -le' $data = q[ABCDEF01]; printf "%X\n", hex $data '
ABCDEF01
$ perl -le' $data = q[ABCDEF01]; printf "%X\n", hex( $data ) >> 8 '
ABCDEF
$ perl -le' $data = q[ABCDEF01]; printf "%X\n", hex( $data ) >> 10 '
2AF37B
John
--
use Perl;
program
fulfillment
------------------------------
Date: Fri, 9 Nov 2007 10:44:06 +0000
From: Ben Morrow <ben@morrow.me.uk>
Subject: Re: make on TK fails on Solaris 10
Message-Id: <m8qd05-pob.ln1@osiris.mauzo.dyndns.org>
Quoth mariakvelasco@gmail.com:
>
> We are in need of some help or suggestions. We are trying to build the
> TK modules on Solaris 10. We downloaded Tk-804.027.tar.gz from CPAN
> and extracted the compressed tarfile using gunzip and tar, then we
> created the makefile by running the command perl Makefile.PL, which
> succeeded. However, when we ran make, we get the following errors:
>
> cd pTk && make DEFINE=""
> cd zlib && make libz.a "CC=cc" RANLIB=":"
> `libz.a' is up to date.
> cc -c -I/usr/perl5/site_perl/5.8.4/sun4-solaris-64int/Tk -Ilibpng -
> Izlib -I/usr/openwin/include -D_LARGEFILE_SOURCE -
> D_FILE_OFFSET_BITS=64 -D_TS_ERRNO -DVERSION=\"4.003\" -DXS_VERSION=
> \"800.025\" "-I/usr/perl5/5.8.4/lib/sun4-solaris-64int/CORE" PNG.c
> PNG.xs:26: warning: data definition has no type or storage class
> PNG.xs: In function `boot_Tk__PNG':
> PNG.xs:35: `IMPORT_PHOTO' undeclared (first use in this function)
IMPORT_PHOTO is #defined in vtab.def, which is included from tkGlue.h,
which is included from PNG.xs. Since your cc didn't report being unable
to include those files, I presume it was finding incorrect versions. Do
you already have an install of Tk in
/usr/perl5/site_perl/5.8.4/sun4-solaris-64int/Tk ? I don't really
understand why you are getting a -I switch for that directory rather
than for /tmp/Tk-804.027 . If you do have an older version of Tk
installed, it might be worth removing it first.
Otherwise, is there some switch you can give to your cc that will tell
you where it's finding each include file (often running a file through
cc -E, with all the other switches in the commandline above, will give
you a preprocessed file with #line directives in) so we can see what's
going on?
Ben
------------------------------
Date: Fri, 09 Nov 2007 08:10:34 GMT
From: tadmc@seesig.invalid
Subject: Posting Guidelines for comp.lang.perl.misc ($Revision: 1.8 $)
Message-Id: <_BUYi.2230$TR5.1937@nlpi061.nbdc.sbc.com>
Outline
Before posting to comp.lang.perl.misc
Must
- Check the Perl Frequently Asked Questions (FAQ)
- Check the other standard Perl docs (*.pod)
Really Really Should
- Lurk for a while before posting
- Search a Usenet archive
If You Like
- Check Other Resources
Posting to comp.lang.perl.misc
Is there a better place to ask your question?
- Question should be about Perl, not about the application area
How to participate (post) in the clpmisc community
- Carefully choose the contents of your Subject header
- Use an effective followup style
- Speak Perl rather than English, when possible
- Ask perl to help you
- Do not re-type Perl code
- Provide enough information
- Do not provide too much information
- Do not post binaries, HTML, or MIME
Social faux pas to avoid
- Asking a Frequently Asked Question
- Asking a question easily answered by a cursory doc search
- Asking for emailed answers
- Beware of saying "doesn't work"
- Sending a "stealth" Cc copy
Be extra cautious when you get upset
- Count to ten before composing a followup when you are upset
- Count to ten after composing and before posting when you are upset
-----------------------------------------------------------------
Posting Guidelines for comp.lang.perl.misc ($Revision: 1.8 $)
This newsgroup, commonly called clpmisc, is a technical newsgroup
intended to be used for discussion of Perl related issues (except job
postings), whether it be comments or questions.
As you would expect, clpmisc discussions are usually very technical in
nature and there are conventions for conduct in technical newsgroups
going somewhat beyond those in non-technical newsgroups.
The article at:
http://www.catb.org/~esr/faqs/smart-questions.html
describes how to get answers from technical people in general.
This article describes things that you should, and should not, do to
increase your chances of getting an answer to your Perl question. It is
available in POD, HTML and plain text formats at:
http://www.rehabitation.com/clpmisc.shtml
For more information about netiquette in general, see the "Netiquette
Guidelines" at:
http://andrew2.andrew.cmu.edu/rfc/rfc1855.html
A note to newsgroup "regulars":
Do not use these guidelines as a "license to flame" or other
meanness. It is possible that a poster is unaware of things
discussed here. Give them the benefit of the doubt, and just
help them learn how to post, rather than assume that they do
know and are being the "bad kind" of Lazy.
A note about technical terms used here:
In this document, we use words like "must" and "should" as
they're used in technical conversation (such as you will
encounter in this newsgroup). When we say that you *must* do
something, we mean that if you don't do that something, then
it's unlikely that you will benefit much from this group.
We're not bossing you around; we're making the point without
lots of words.
Do *NOT* send email to the maintainer of these guidelines. It will be
discarded unread. The guidelines belong to the newsgroup so all
discussion should appear in the newsgroup. I am just the secretary that
writes down the consensus of the group.
Before posting to comp.lang.perl.misc
Must
This section describes things that you *must* do before posting to
clpmisc, in order to maximize your chances of getting meaningful replies
to your inquiry and to avoid getting flamed for being lazy and trying to
have others do your work.
The perl distribution includes documentation that is copied to your hard
drive when you install perl. Also installed is a program for looking
things up in that (and other) documentation named 'perldoc'.
You should either find out where the docs got installed on your system,
or use perldoc to find them for you. Type "perldoc perldoc" to learn how
to use perldoc itself. Type "perldoc perl" to start reading Perl's
standard documentation.
Check the Perl Frequently Asked Questions (FAQ)
Checking the FAQ before posting is required in Big 8 newsgroups in
general, there is nothing clpmisc-specific about this requirement.
You are expected to do this in nearly all newsgroups.
You can use the "-q" switch with perldoc to do a word search of the
questions in the Perl FAQs.
Check the other standard Perl docs (*.pod)
The perl distribution comes with much more documentation than is
available for most other newsgroups, so in clpmisc you should also
see if you can find an answer in the other (non-FAQ) standard docs
before posting.
It is *not* required, or even expected, that you actually *read* all of
Perl's standard docs, only that you spend a few minutes searching them
before posting.
Try doing a word-search in the standard docs for some words/phrases
taken from your problem statement or from your very carefully worded
"Subject:" header.
Really Really Should
This section describes things that you *really should* do before posting
to clpmisc.
Lurk for a while before posting
This is very important and expected in all newsgroups. Lurking means
to monitor a newsgroup for a period to become familiar with local
customs. Each newsgroup has specific customs and rituals. Knowing
these before you participate will help avoid embarrassing social
situations. Consider yourself to be a foreigner at first!
Search a Usenet archive
There are tens of thousands of Perl programmers. It is very likely
that your question has already been asked (and answered). See if you
can find where it has already been answered.
One such searchable archive is:
http://groups.google.com/advanced_group_search
If You Like
This section describes things that you *can* do before posting to
clpmisc.
Check Other Resources
You may want to check in books or on web sites to see if you can
find the answer to your question.
But you need to consider the source of such information: there are a
lot of very poor Perl books and web sites, and several good ones
too, of course.
Posting to comp.lang.perl.misc
There can be 200 messages in clpmisc in a single day. Nobody is going to
read every article. They must decide somehow which articles they are
going to read, and which they will skip.
Your post is in competition with 199 other posts. You need to "win"
before a person who can help you will even read your question.
These sections describe how you can help keep your article from being
one of the "skipped" ones.
Is there a better place to ask your question?
Question should be about Perl, not about the application area
It can be difficult to separate out where your problem really is,
but you should make a conscious effort to post to the most
applicable newsgroup. That is, after all, where you are the most
likely to find the people who know how to answer your question.
Being able to "partition" a problem is an essential skill for
effectively troubleshooting programming problems. If you don't get
that right, you end up looking for answers in the wrong places.
It should be understood that you may not know that the root of your
problem is not Perl-related (the two most frequent ones are CGI and
Operating System related), so off-topic postings will happen from
time to time. Be gracious when someone helps you find a better place
to ask your question by pointing you to a more applicable newsgroup.
How to participate (post) in the clpmisc community
Carefully choose the contents of your Subject header
You have 40 precious characters of Subject to win out and be one of
the posts that gets read. Don't waste them. Take care while
composing them, they are the key that opens the door to getting an
answer.
Spend them indicating what aspect of Perl others will find if they
should decide to read your article.
Do not spend them indicating "experience level" (guru, newbie...).
Do not spend them pleading (please read, urgent, help!...).
Do not spend them on non-Subjects (Perl question, one-word
Subject...)
For more information on choosing a Subject see "Choosing Good
Subject Lines":
http://www.cpan.org/authors/id/D/DM/DMR/subjects.post
Part of the beauty of newsgroup dynamics, is that you can contribute
to the community with your very first post! If your choice of
Subject leads a fellow Perler to find the thread you are starting,
then even asking a question helps us all.
Use an effective followup style
When composing a followup, quote only enough text to establish the
context for the comments that you will add. Always indicate who
wrote the quoted material. Never quote an entire article. Never
quote a .signature (unless that is what you are commenting on).
Intersperse your comments *following* each section of quoted text to
which they relate. Unappreciated followup styles are referred to as
"top-posting", "Jeopardy" (because the answer comes before the
question), or "TOFU" (Text Over, Fullquote Under).
Reversing the chronology of the dialog makes it much harder to
understand (some folks won't even read it if written in that style).
For more information on quoting style, see:
http://web.presby.edu/~nnqadmin/nnq/nquote.html
Speak Perl rather than English, when possible
Perl is much more precise than natural language. Saying it in Perl
instead will avoid misunderstanding your question or problem.
Do not say: I have variable with "foo\tbar" in it.
Instead say: I have $var = "foo\tbar", or I have $var = 'foo\tbar',
or I have $var = <DATA> (and show the data line).
Ask perl to help you
You can ask perl itself to help you find common programming mistakes
by doing two things: enable warnings (perldoc warnings) and enable
"strict"ures (perldoc strict).
You should not bother the hundreds/thousands of readers of the
newsgroup without first seeing if a machine can help you find your
problem. It is demeaning to be asked to do the work of a machine. It
will annoy the readers of your article.
You can look up any of the messages that perl might issue to find
out what the message means and how to resolve the potential mistake
(perldoc perldiag). If you would like perl to look them up for you,
you can put "use diagnostics;" near the top of your program.
Do not re-type Perl code
Use copy/paste or your editor's "import" function rather than
attempting to type in your code. If you make a typo you will get
followups about your typos instead of about the question you are
trying to get answered.
Provide enough information
If you do the things in this item, you will have an Extremely Good
chance of getting people to try and help you with your problem!
These features are a really big bonus toward your question winning
out over all of the other posts that you are competing with.
First make a short (less than 20-30 lines) and *complete* program
that illustrates the problem you are having. People should be able
to run your program by copy/pasting the code from your article. (You
will find that doing this step very often reveals your problem
directly. Leading to an answer much more quickly and reliably than
posting to Usenet.)
Describe *precisely* the input to your program. Also provide example
input data for your program. If you need to show file input, use the
__DATA__ token (perldata.pod) to provide the file contents inside of
your Perl program.
Show the output (including the verbatim text of any messages) of
your program.
Describe how you want the output to be different from what you are
getting.
If you have no idea at all of how to code up your situation, be sure
to at least describe the 2 things that you *do* know: input and
desired output.
Do not provide too much information
Do not just post your entire program for debugging. Most especially
do not post someone *else's* entire program.
Do not post binaries, HTML, or MIME
clpmisc is a text only newsgroup. If you have images or binaries
that explain your question, put them in a publically accessible
place (like a Web server) and provide a pointer to that location. If
you include code, cut and paste it directly in the message body.
Don't attach anything to the message. Don't post vcards or HTML.
Many people (and even some Usenet servers) will automatically filter
out such messages. Many people will not be able to easily read your
post. Plain text is something everyone can read.
Social faux pas to avoid
The first two below are symptoms of lots of FAQ asking here in clpmisc.
It happens so often that folks will assume that it is happening yet
again. If you have looked but not found, or found but didn't understand
the docs, say so in your article.
Asking a Frequently Asked Question
It should be understood that you may have missed the applicable FAQ
when you checked, which is not a big deal. But if the Frequently
Asked Question is worded similar to your question, folks will assume
that you did not look at all. Don't become indignant at pointers to
the FAQ, particularly if it solves your problem.
Asking a question easily answered by a cursory doc search
If folks think you have not even tried the obvious step of reading
the docs applicable to your problem, they are likely to become
annoyed.
If you are flamed for not checking when you *did* check, then just
shrug it off (and take the answer that you got).
Asking for emailed answers
Emailed answers benefit one person. Posted answers benefit the
entire community. If folks can take the time to answer your
question, then you can take the time to go get the answer in the
same place where you asked the question.
It is OK to ask for a *copy* of the answer to be emailed, but many
will ignore such requests anyway. If you munge your address, you
should never expect (or ask) to get email in response to a Usenet
post.
Ask the question here, get the answer here (maybe).
Beware of saying "doesn't work"
This is a "red flag" phrase. If you find yourself writing that,
pause and see if you can't describe what is not working without
saying "doesn't work". That is, describe how it is not what you
want.
Sending a "stealth" Cc copy
A "stealth Cc" is when you both email and post a reply without
indicating *in the body* that you are doing so.
Be extra cautious when you get upset
Count to ten before composing a followup when you are upset
This is recommended in all Usenet newsgroups. Here in clpmisc, most
flaming sub-threads are not about any feature of Perl at all! They
are most often for what was seen as a breach of netiquette. If you
have lurked for a bit, then you will know what is expected and won't
make such posts in the first place.
But if you get upset, wait a while before writing your followup. I
recommend waiting at least 30 minutes.
Count to ten after composing and before posting when you are upset
After you have written your followup, wait *another* 30 minutes
before committing yourself by posting it. You cannot take it back
once it has been said.
AUTHOR
Tad McClellan and many others on the comp.lang.perl.misc newsgroup.
--
Tad McClellan
email: perl -le "print scalar reverse qq/moc.noitatibaher\100cmdat/"
------------------------------
Date: 09 Nov 2007 09:05:07 GMT
From: T <myicq2@3gmx.net4>
Subject: Re: script to make font as a grid in plain text?
Message-Id: <Xns99E36695CDF18myicqgmxnet@212.242.40.162>
RedGrittyBrick <RedGrittyBrick@SpamWeary.foo> wrote in news:47332e6b$0
$21088$da0feed9@news.zen.co.uk:
> It seems unlikely to me. It looks like a rather rare and arcane sort of
> requirement. Wouldn't you have to pass the font data through a Truetype
> rendering engine so that the font's hinting algorithms are processed?
That may be another way. Where do I ask how it's done (as a simple
example)?
All I need to have "Font X" rendered in a certain size onto a grid,
to be used in an ANSI C application.
You are welcome to mail me personally, just remove numbers from the mail.
Thank you.
------------------------------
Date: Fri, 9 Nov 2007 10:55:22 +0000
From: Ben Morrow <ben@morrow.me.uk>
Subject: Re: Set TCP_MAXSEG (OS buffering) on Win32? How?
Message-Id: <qtqd05-pob.ln1@osiris.mauzo.dyndns.org>
Quoth Ed W <ed@notarealemailaccount.com>:
> For various reasons I have a requirement to have an app listening on
> localhost which is proxying output from another app that is not under my
> control. Currently the OS is buffering too much data (I think >XP the OS
> buffers >64KB ish?) and I need to try and find a way to crank down the
> OS buffers without making a system wide registry change
>
> The solution appeared to be to use the TCP_MAXSEG option:
> setsockopt($server, &Socket::IPPROTO_TCP, &Socket::TCP_MAXSEG, 2048);
Don't call subs with &. Not even constants.
> However, on activestate at least this is giving me:
> Your vendor has not defined Socket macro TCP_MAXSEG, used at xxx
So Socket doesn't know about TCP_MAXSEG. One way around is to find out
what its value should be (from MSDN) and specify it directly. Another
(better, but probably *much* harder on Win32) is to rebuild perl in such
a way that it can find out for itself, since Socket does know about
TCP_MAXSEG on some platforms.
Ben
------------------------------
Date: Fri, 09 Nov 2007 11:03:05 +0000
From: RedGrittyBrick <RedGrittyBrick@SpamWeary.foo>
Subject: Re: SOAP server & client problem
Message-Id: <47343e6e$0$8413$db0fefd9@news.zen.co.uk>
Some1 wrote:
> Hello All,
>
> I have written SOAP client send two variables "two massages" , also I
I think you mean "messages". Massages are something completely different :-)
SOAP::Lite is more of a RPC implementation than a message-passing
implementation so it would be clearer to refer to passing arguments to
subroutine parameters or, in OO terms, to method parameters.
> have written SOAP server accept one variable.
Your SOAP service includes a method that expects a single argument.
> My problem I want the soap server accept two variables "two massages"
You want the method to accept two arguments?
> and replay with results.
I think you mean "reply" with a single string. Replay means: to repeat
the method call with the same arguments.
>
> Helle.pm file
You mean Hello.pm.
> ======================
> package Hello;
> sub sayHello {
> shift;
>
> return "Hello Jack" if shift eq "Jack";
This should work but I find it clearer to write
my ($class, $firstname) = @_;
etc.
>
> die "Sorry..\n";
>
> }
>
> 1;
>
>
>
> hello.cgi
> ===============================
> #!/usr/bin/perl -w
>
>
> use lib '/var/www/cgi-bin/Hello';
You shouldn't need the line above.
> use SOAP::Transport::HTTP;
> SOAP::Transport::HTTP::CGI
> -> dispatch_to('Hello::(?:sayHello)')
The line above looks odd to me. I'd have
-> dispatch_to("/var/www/cgi-bin")
> -> handle
> ;
> #############################
> Hello.pm and hello.cgi all of them in the same folder /var/www/cgi-bin
>
>
>
> Now the soap client script hclient.pl:
> ===============================
> #!/usr/bin/perl -w
use strict;
>
> use SOAP::Lite;
>
> my $name = shift;
> my $lname = shift ;
> print "\n\nCalling the SOAP Server to say hello\n\n";
> print "The SOAP Server says: \n";
> print SOAP::Lite
> -> uri('urn:Hello')
> -> proxy('http://homesrv/cgi-bin/hello.cgi')
*Always* check for error messages!
-> on_fault(sub { my($soap, $res) = @_;
die ref $res ? $res->faultstring
: $soap->transport->status, "\n";
})
> -> sayHello($name,$lname)
> -> result . "\n\n";
>
> ##############################END##################################3
>
>
> If I run "perl hclient.pl Jack" it is working fine, but when I tried
> "perl hclient.pl Jack King" it will not work... why?
"will not work" is too vague.
The posting guidelines, which are rugularly posted to this newsgroup, say
Show the output (including the verbatim text of any messages) of
your program.
Describe how you want the output to be different from what you are
getting.
> by the way Jack is variable 1 and King variable 2, I want my soap
> server accept all the variables.
>
> Could you please guide me where is my mistake or how to fix it?
>
You made the following mistakes:
- Not reading the posting guidelines
- Not using strict
- Not checking for errors
Your client and module run as I would expect them to.
C:> perl hello.pl Jack Plum
Calling the SOAP Server to say hello
The SOAP Server says:
Hello Jack
C:>
Since you didn't explain how the output differred from what you
expected, I can't tell if there's anything else that needs fixing.
------------------------------
Date: Fri, 09 Nov 2007 13:54:11 -0000
From: Some1 <waleed.harbi@gmail.com>
Subject: Re: SOAP server & client problem
Message-Id: <1194616451.021987.76020@e9g2000prf.googlegroups.com>
Hi,
Thank you RedGrittyBrick.
I did C:> perl hello.pl Jack Plum
but I want the result : Hello Jack Plum
if you miss Plum, I want the soap reply with error message.
Thank a lot for your comments RedGrittyBrick.
On Nov 9, 2:03 pm, RedGrittyBrick <RedGrittyBr...@SpamWeary.foo>
wrote:
> Some1 wrote:
> > Hello All,
>
> > I have written SOAP client send two variables "two massages" , also I
>
> I think you mean "messages". Massages are something completely different :-)
>
> SOAP::Lite is more of a RPC implementation than a message-passing
> implementation so it would be clearer to refer to passing arguments to
> subroutine parameters or, in OO terms, to method parameters.
>
> > have written SOAP server accept one variable.
>
> Your SOAP service includes a method that expects a single argument.
>
> > My problem I want the soap server accept two variables "two massages"
>
> You want the method to accept two arguments?
>
> > and replay with results.
>
> I think you mean "reply" with a single string. Replay means: to repeat
> the method call with the same arguments.
>
>
>
> > Helle.pm file
>
> You mean Hello.pm.
>
> > ======================
> > package Hello;
> > sub sayHello {
> > shift;
>
> > return "Hello Jack" if shift eq "Jack";
>
> This should work but I find it clearer to write
> my ($class, $firstname) = @_;
> etc.
>
>
>
> > die "Sorry..\n";
>
> > }
>
> > 1;
>
> > hello.cgi
> > ===============================
> > #!/usr/bin/perl -w
>
> > use lib '/var/www/cgi-bin/Hello';
>
> You shouldn't need the line above.
>
> > use SOAP::Transport::HTTP;
> > SOAP::Transport::HTTP::CGI
> > -> dispatch_to('Hello::(?:sayHello)')
>
> The line above looks odd to me. I'd have
> -> dispatch_to("/var/www/cgi-bin")
>
> > -> handle
> > ;
> > #############################
> > Hello.pm and hello.cgi all of them in the same folder /var/www/cgi-bin
>
> > Now the soap client script hclient.pl:
> > ===============================
> > #!/usr/bin/perl -w
>
> use strict;
>
>
>
> > use SOAP::Lite;
>
> > my $name = shift;
> > my $lname = shift ;
> > print "\n\nCalling the SOAP Server to say hello\n\n";
> > print "The SOAP Server says: \n";
> > print SOAP::Lite
> > -> uri('urn:Hello')
> > -> proxy('http://homesrv/cgi-bin/hello.cgi')
>
> *Always* check for error messages!
>
> -> on_fault(sub { my($soap, $res) = @_;
> die ref $res ? $res->faultstring
> : $soap->transport->status, "\n";
> })
>
> > -> sayHello($name,$lname)
> > -> result . "\n\n";
>
> > ##############################END##################################3
>
> > If I run "perl hclient.pl Jack" it is working fine, but when I tried
> > "perl hclient.pl Jack King" it will not work... why?
>
> "will not work" is too vague.
> The posting guidelines, which are rugularly posted to this newsgroup, say
>
> Show the output (including the verbatim text of any messages) of
> your program.
>
> Describe how you want the output to be different from what you are
> getting.
>
> > by the way Jack is variable 1 and King variable 2, I want my soap
> > server accept all the variables.
>
> > Could you please guide me where is my mistake or how to fix it?
>
> You made the following mistakes:
> - Not reading the posting guidelines
> - Not using strict
> - Not checking for errors
>
> Your client and module run as I would expect them to.
>
> C:> perl hello.pl Jack Plum
>
> Calling the SOAP Server to say hello
>
> The SOAP Server says:
> Hello Jack
>
> C:>
>
> Since you didn't explain how the output differred from what you
> expected, I can't tell if there's anything else that needs fixing.
------------------------------
Date: Fri, 09 Nov 2007 11:22:56 +0100
From: Michele Dondi <bik.mido@tiscalinet.it>
Subject: Re: Why can't you slice an array @a[3..-1]?
Message-Id: <htc8j3l9vsivighpchtd3ipp1589673h63@4ax.com>
On Thu, 08 Nov 2007 19:15:43 -0600, Clint Olsen
<clint.olsen@gmail.com> wrote:
>This doesn't work for array references. How can I perform the same ($#) on
>an array reference?
>
>I got this when trying to:
>
>DB<10> x $#{@$_}
>Bizarre copy of ARRAY in leave at (eval
>76)[/nfs/pdx/disks/pdx_otools/lib/perl5/5.8.5/perl5db.pl:620] line 2.
>
>And $_ is an array reference.
It does work. Of course you're not dereferencing the right way, AND it
must be a NAMED reference.
pilsner:~ [11:22:48]$ perl -le '$a=[1..5];print @$a[3..$#$a]'
45
Michele
--
{$_=pack'B8'x25,unpack'A8'x32,$a^=sub{pop^pop}->(map substr
(($a||=join'',map--$|x$_,(unpack'w',unpack'u','G^<R<Y]*YB='
.'KYU;*EVH[.FHF2W+#"\Z*5TI/ER<Z`S(G.DZZ9OX0Z')=~/./g)x2,$_,
256),7,249);s/[^\w,]/ /g;$ \=/^J/?$/:"\r";print,redo}#JAPH,
------------------------------
Date: Fri, 09 Nov 2007 11:25:06 +0100
From: Michele Dondi <bik.mido@tiscalinet.it>
Subject: Re: Why can't you slice an array @a[3..-1]?
Message-Id: <v9d8j3dpk94grr2r8nu3quso37b9ptig69@4ax.com>
On Thu, 08 Nov 2007 19:34:05 -0600, Clint Olsen
<clint.olsen@gmail.com> wrote:
>$#$_
>
>Where $_ is an array reference. I can't explain why this works however
>based on my knowledge of perl and references...
It's kind of a corner case. The whole $#array thing is rather ugly
IMHO. Perl 6 will have suitable methods instead.
Michele
--
{$_=pack'B8'x25,unpack'A8'x32,$a^=sub{pop^pop}->(map substr
(($a||=join'',map--$|x$_,(unpack'w',unpack'u','G^<R<Y]*YB='
.'KYU;*EVH[.FHF2W+#"\Z*5TI/ER<Z`S(G.DZZ9OX0Z')=~/./g)x2,$_,
256),7,249);s/[^\w,]/ /g;$ \=/^J/?$/:"\r";print,redo}#JAPH,
------------------------------
Date: Fri, 09 Nov 2007 03:37:50 -0800
From: Paul Lalli <mritty@gmail.com>
Subject: Re: Why can't you slice an array @a[3..-1]?
Message-Id: <1194608270.131337.132840@57g2000hsv.googlegroups.com>
On Nov 9, 5:22 am, Michele Dondi <bik.m...@tiscalinet.it> wrote:
> It does work. Of course you're not dereferencing the right way,
> AND it must be a NAMED reference.
Says who?
$ perl -le'print $#{[qw/a b c d e/]}'
4
Paul Lalli
------------------------------
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:
#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.
NOTE: due to the current flood of worm email banging on ruby, the smtp
server on ruby has been shut off until further notice.
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.
#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 1018
***************************************
