[26401] in Perl-Users-Digest
Perl-Users Digest, Issue: 8572 Volume: 10
daemon@ATHENA.MIT.EDU (Perl-Users Digest)
Wed Oct 26 11:05:38 2005
Date: Wed, 26 Oct 2005 08:05:05 -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 Wed, 26 Oct 2005 Volume: 10 Number: 8572
Today's topics:
Re: Access a c++ module from Perl <"harryfmudd [AT] comcast [DOT] net">
Web form CGI, Security? <newsAT@screenlightDOT.com>
Digest Administrivia (Last modified: 6 Apr 01) (Perl-Users-Digest Admin)
----------------------------------------------------------------------
Date: Wed, 26 Oct 2005 10:45:41 -0400
From: "harryfmudd [AT] comcast [DOT] net" <"harryfmudd [AT] comcast [DOT] net">
Subject: Re: Access a c++ module from Perl
Message-Id: <fq6dnQhwU5kLC8LeRVn-iA@comcast.com>
bg-greece wrote:
> You mean I should create the DLL with cygwin/gcc?
> Putting aside that it needs a lot of time to do the porting, it contradicts
> the fact that I can perfectly call Windows system DLL's like user32,
> kernel32 and so on using Win32::API.
Well, to be honest I have never done what you're trying to do FROM
CYGWIN. I also note that someone has, because Win32-Process-Info 1.006
has a "pass" from Cygwin (see
http://testers.cpan.org/show/Win32-Process-Info.html).
On the other hand, if you have the calling sequence right (as you say
you do) and if the version of C doesn't matter (as you say it doesn't),
then we just proved your code works.
But it doesn't. At this point, I generally ask myself "what is it that I
know to be true, but which is in fact not true?". The possibilities seem
to me to be:
1) the calling sequence is in fact coded incorrectly in Perl. I have no
experience with the prototype version of the interface, but the
traditional interface call in Bart Lateur's response looks right to me
given the C signature in your original note, and you say that didn't work.
2) Different compilers _can_ produce different calling sequences, so
that's what I was focusing on. You say calls to Kernel32 work, which
suggests that this isn't the problem, but doesn't prove it, since we
don't know that Kernel32 was written in Visual C++. But we _do_ know
that Visual C++ can call kernel32.dll. Have you read kernel32.h, and
made sure your signatures are specified the same way? C++ wants to
mangle function names (that's how overloading works), and it's possible
that there is more than one way to handle the call stack. A mangled
function name would probably result in a failure to import the function,
but there are probably other things that could go wrong.
3) Something else entirely. Arthur Conan Doyle was wrong when he had
Sherlock Holmes say something like "When you have eliminated everything
else, the remaining possibility, however improbable, must be the truth."
The problem with the Sherlock Holmes approach is that it assumes you
really know what every single possibility is.
Tom Wyant
------------------------------
Date: Wed, 26 Oct 2005 13:54:58 GMT
From: one man army <newsAT@screenlightDOT.com>
Subject: Web form CGI, Security?
Message-Id: <newsAT-49100E.06580226102005@newsclstr02.news.prodigy.com>
I would like to generate a few simple web forms. Is the Perl CGI, and a
cgi-enabled directory, a huge security hole?
I read the lines that say to disable upload, and limit the size of a
POST.
I'm asking my host to install CGI, although I know he is security
conscious.
thanks for your informed opinions
------------------------------
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 V10 Issue 8572
***************************************
