Message-Id: <34BA5C2C.79C39B7E@lps.u-psud.fr> Date: Mon, 12 Jan 1998 20:08:44 +0200 From: Daniel Taupin Mime-Version: 1.0 To: molnarl AT cdata DOT tvnet DOT hu, Latex2html list , DJGPP List Subject: Re: perl54b.zip bugged References: Content-Type: multipart/alternative; boundary="------------DAAFB6C9B0E0BF4450DEE5F2" Precedence: bulk --------------DAAFB6C9B0E0BF4450DEE5F2 Content-Type: text/plain; charset=iso-8859-1 Content-Transfer-Encoding: 8bit molnarl AT cdata DOT tvnet DOT hu wrote: > I just checked perl 5.004_02, and didn't find this "unable to load" string > in the distribution. What is this message EXACTLY? > > > > bug. If it's a real bug I'll upload a new binary distribution of > > > perl5.004_04 to DJ. > > According to the perl changelog, the latest memory related problem was > corrected in 5.004_02. What does go32-v2.exe say to you? What I can say is that the "Out of memory!" message happens in the following perl command (which I do not understand at all: explanations welcome): s/((\%|$comment_mark)\n|.)\n{2,}/$1\n\\par\n/og; > As you can see, the difference of behaviour in Win 3.11 and Win95 make me think the problem might be due to perl (unlikely > libgdbm.a). That's why I would appreciate a vew version of perl, whose memory management would be safe... > > > Laszlo -- ------------------------------------------------------------------------- Daniel Taupin, Physique des Solides, Univ. Paris-Sud, 91405 ORSAY E-mail : mailto:taupin AT lps DOT u-psud DOT fr Tél: (33) 1.69.15.60.79, Fax: (33) 1.69.15.60.86 ------------------------------------------------------------------------- --------------DAAFB6C9B0E0BF4450DEE5F2 Content-Type: text/html; charset=us-ascii Content-Transfer-Encoding: 7bit

molnarl AT cdata DOT tvnet DOT hu wrote:

I just checked perl 5.004_02, and didn't find this "unable to load" string
in the distribution. What is this message EXACTLY?
> > bug. If it's a real bug I'll upload a new binary distribution of
> > perl5.004_04 to DJ.

According to the perl changelog, the latest memory related problem was
corrected in 5.004_02. What does go32-v2.exe say to you?

What I can say is that the "Out of memory!" message happens in the following perl command (which I do not understand at all: explanations welcome):

s/((\%|$comment_mark)\n|.)\n{2,}/$1\n\\par\n/og;

As you can see, the difference of behaviour in Win 3.11 and Win95 make me think the problem might be due to perl (unlikely libgdbm.a).

That's why I would appreciate a vew version of perl, whose memory management would be safe...

Laszlo

--
-------------------------------------------------------------------------
Daniel Taupin, Physique des Solides, Univ. Paris-Sud, 91405 ORSAY
E-mail : mailto:taupin AT lps DOT u-psud DOT fr
Tél: (33) 1.69.15.60.79, Fax: (33) 1.69.15.60.86
-------------------------------------------------------------------------
--------------DAAFB6C9B0E0BF4450DEE5F2--