- Original Message -
From: "Foo Ji-Haw" <[EMAIL PROTECTED]>
To: "Sisyphus" <[EMAIL PROTECTED]>
Cc:
Sent: Tuesday, February 21, 2006 5:42 PM
Subject: Re: Tough qn: understanding this (C) error while using inline
> Hello guys,
>
> Loading the library helped. I think I've hit the problem
Hello guys,
Loading the library helped. I think I've hit the problem you foresaw.
ULONG returns an error during compilation:
error C2275: 'ULONG' : illegal use of this type as an expression
Is it to do with typemaps? I tried to find some good documentation, but
the only example I got was:
ht
Maurice Height wrote:
> I have just solved a bug in my code involving a compiled regex.
> I am wondering if I have got it wrong or if this is a Perl error.
> To explain...
>
> I had a class ABC in which I passed a value to the constructor
> (eg: $arg{delim_str} ) and stored this for later use thr
I have just solved a bug in my code involving a compiled regex.
I am wondering if I have got it wrong or if this is a Perl error.
To explain...
I had a class ABC in which I passed a value to the constructor
(eg: $arg{delim_str} ) and stored this for later use throughout the class:
$self->{DELI
Hello Reinhard, Sisyphus, Mark,
Thanks for the helping me past the first roadblock. I am trying to see
how far I can get with this TAPI implementation (despite my noobness at
inline coding). I hope I can continue to engage your help through my
endeavour.
As promised. If I actually got anywhe
Try separating the username & password with a colon.
KCOn 2/14/06, Jerry Kassebaum <[EMAIL PROTECTED]> wrote:
The code below is modified from Suehring's "Beginning Perl Web Development". I'm thinking it is supposed to get me the format for entering my usernameand password. However, the result I g
I will be out of the office starting 02/20/2005 and will not return until
02/27/2006.
The information contained in this message may be CONFIDENTIAL and is for the
intended addressee only. Any unauthorized use, dissemination of the
information, or copying of this message is prohibited. If
Hi Chaddaï
My simplistic understanding (and I'm no Perl internals developer- just a user) is that there are several reasons;
One: SSL steps on a lot of patents- Even SSLeay is pretty "underground" these days.
Two: Threading appears to always be an issue with SSL integration... at
least it
At 09:50 AM 2/20/2006 -0500, D D Allen wrote:
And then try to explain these lines -- why the first produces the output
10 and the second produces the output 30 -- which is not a Perl bug.
print (5*2)*3;
print "\n";
print 5*(2*3);
print "\n";
As Larry Wall says in the Camel book: If it looks
At 09:50 AM 2/20/2006 -0500, D D Allen wrote:
>And then try to explain these lines -- why the first produces the output
>10 and the second produces the output 30 -- which is not a Perl bug.
>
>print (5*2)*3;
>print "\n";
>print 5*(2*3);
>print "\n";
Yep I've gotten burned several times with that
You're not necessarily wrong... or right.
As indicated by many of the responses, you've used a Perl construct
that is an "edge condition" in the language whose behavior isn't
well defined. But it's also a dubious programming construct in any
language. Translating that statement to english, "con
- Original Message -
From: "Reinhard Pagitsch"
> >
> Could it be because I use Perl v5.6.1? It worked the way I replayed.
>
If it works on 5.6.1, it probably also works on 5.8.x it just seems an
odd way of going about it (to me). The '-L' switch is normally used to
designate a dire
Sisyphus wrote:
- Original Message -
From: "Foo Ji-Haw" <[EMAIL PROTECTED]>
To:
Sent: Friday, February 17, 2006 7:54 PM
Subject: Tough qn: understanding this (C) error while using inline
Hi all,
I'm trying my first hand at writing some C code to extend TAPI onto Perl
using inlin
13 matches
Mail list logo
