Re: Re (tilly) 1: What Happened...(perils of porting from c)

in reply to Re (tilly) 1: What Happened...(perils of porting from c)
in thread What Happened...(perils of porting from c)

Hey thanx for the critique ...

Added "use strict" , switched to a perl aware editor (boy that caught alot just switching editors)(changed @curlevel to $curlevel..the GOOD editor caught that)

split up the stmt that had the "||" in it (that somehow fixed that), fixed the munged comments, and that oneline for loop. Now no syntax errors (yeah!)

Mostly i am looking for someone to tell me if i got the pointer arithmetic related crap ported right .. when i use the module i'm getting some nonsense output (examples are uploaded to here).

One thing why get rid of the "return 1;" at the end? every example of writing a module says it should return "1" to signal proper loading.

Comment on Re: Re (tilly) 1: What Happened...(perils of porting from c)

Replies are listed 'Best First'.
Re (tilly) 3: What Happened...(perils of porting from c) by tilly (Archbishop) on Jan 05, 2001 at 22:35 UTC
The reason for removing the return statement is that you are not supposed to use that outside of functions (eval, do). Just end with: `1;` [download] and it will work. As for the pointer logic, sorry. No energy to go through it. It looked like a mess FWIW. I would just use recursion for this problem. (OK, so you take a performance hit.)	[reply] [d/l]

In Section Seekers of Perl Wisdom