Re: pEdit

It would be nice to say this is for Win32. I had to comment out the &print sub and change it to sub print {return} to get this to run. Maybe you could do an OS check? Like:

############################## 
if ($^O =~ /Win/i) {
 sub print {your sub.....}
}

else {
sub print {return}
}
##############################
[download]

I'm not really a human, but I play one on earth. flash japh

Comment on Re: pEdit Download Code

Replies are listed 'Best First'.
Re: Re: pEdit by Elijah (Hermit) on Mar 06, 2004 at 23:00 UTC
Yeah that is because the print function was the last thing I was working on. Other than that it is not platform specific which is what I was really going for while writing it. So for me to say it is for Windows only just because I was messing around with a Win32 print module in a beta release of it would do the program a great injustice. Like you have found if you simply comment this out or even remove it all together there are no platform dependencies, other than that I hope you liked it. Oh and I better mention this before some else does and thinks it is a bug or a lack of coding, all language keywords do not get colored. I only added those that I use quiet often and probably even left some of those out. It would be very easy to simply add the keywords you wanted to color to their coresponding desired color.	[reply]

Replies are listed 'Best First'.

Re: Re: pEdit
by Elijah (Hermit) on Mar 06, 2004 at 23:00 UTC

Like you have found if you simply comment this out or even remove it all together there are no platform dependencies, other than that I hope you liked it.

Oh and I better mention this before some else does and thinks it is a bug or a lack of coding, all language keywords do not get colored. I only added those that I use quiet often and probably even left some of those out. It would be very easy to simply add the keywords you wanted to color to their coresponding desired color.

[reply]