From: Glenn L. <pe...@ne...> - 2004-02-19 19:38:30
|
You should see if you can create a minimum test case that fails, and post the source. Maybe someone can figure it out. I'll be gone a few days though. On approximately 2/19/2004 10:18 AM, came the following characters from the keyboard of ra...@me...: > I am using perl2exe, if I run the scripts that use Win32::API from the > command > line usig perl script.pl, it works normal if I compile to .exe using > perl2exe it > shows the error normally Can not read or write memory address xxxx > but I also tested with perlapp and I got same errors. > > My guess is WIN32::API some how allocate memory or some initilzation > variable(s) that may its data go out of the allocated space for it or > tie(ing) > some variables > > Ramy > > ----- Original Message ----- > From: "Glenn Linderman" <pe...@ne...> > To: <ra...@me...> > Cc: <per...@li...> > Sent: Thursday, February 19, 2004 8:06 PM > Subject: Re: [perl-win32-gui-users] New Win32 Package suggestion and sample > code > > > >>n approximately 2/19/2004 3:01 AM, came the following characters from >>the keyboard of ra...@me...: >> >> >>> but is used by callng WIn32::API which can not >>>currently included with compiled .exe perl scripts >>>therefore it was a must for me to build s little module for this >>>function. >> >>Could you explain the reason for the problem with Win32::API? Maybe the >>solution is to fix Win32::API if it is broken for compile .exe perl >>scripts. What compiler are you using? Do all the compilers have this >>same problem? Maybe it is a bug in the compiler? >> >>-- >>Glenn -- http://nevcal.com/ >>=========================== >>The best part about procrastination is that you are never bored, >>because you have all kinds of things that you should be doing. >> >> > > > > -- Glenn -- http://nevcal.com/ =========================== The best part about procrastination is that you are never bored, because you have all kinds of things that you should be doing. |