Re: Eek! goto?

Since you already have the C code, it shouldn't be too hard to write an Inline::C version. Even if for some reason you don't want to end up with an Inline::C version for production or distribution, you could use the Inline::C function for testing - both the C and the Perl function should return the same values.

And it would also be interesting to benchmark the two.

Abigail

Comment on Re: Eek! goto?

Replies are listed 'Best First'.

Re: Re: Eek! goto?
by BrowserUk (Patriarch) on Feb 12, 2003 at 16:26 UTC

That would be ideal. Unfortunately I am still hamstrung trying to build my own version of Perl using MingW and don't have the money or inclination to shell out for MSVC++ (which is what it appears AS use to build their distributions).

The problem I have hit is

Info: resolving __sys_nerr by linking to __imp___sys_nerr (auto-import
+)
fu000001.o(.idata$3+0xc): undefined reference to `libmsvcrt_a_iname'
nmth000000.o(.idata$4+0x0): undefined reference to `_nm___sys_nerr'
dmake.exe:  Error code 1, while making '..\miniperl.exe'
[download]

Which from google appears to be a problem with the MinGW libraries rather than the perl source as I found evidence of similar problems when it's used to build various other things including CygWin, Ruby and Python. I've found nothing that relates to this problem when building perl, but whilst the docs suggest building Perl for Win32 using MinGW and DMAKE is possible, I've found little real information on the subject so far, and my requests here for assistance have been met with a stoney silence.

It seems noone else has succeeded doing this either...?

Examine what is said, not who speaks.

The 7th Rule of perl club is -- pearl clubs are easily damaged. Use a diamond club instead.

[reply]
[d/l]


There's more than one way to do things
	PerlMonks