RE: [perlce-user] PerlCE and "real" console

[Konovalov, V. <vko...@sp...>]

> > You're right, and having Win32::GUI will be a real 
> advantage there...

...

> 
> by "weight" I mean mostly "size". the Perl tree on my iPAQ is 
> 10.68 mb, 

That number could be greatly reduced.
Not only you can freely delete unused PMs.
I had few working experiments with Archive::Zip and some modules hidden
inside zip archive... but this hase little in common with PerlCE... Also
with many lib files on SD there is no problem with several megabytes more or
less...


> guess the 
> Perl/Tk distribution weights some mb more. compiling  
> Win32::GUI for the 
> CE platform shouldn't (I hope) add much more to the desktop version, 
> which actually is ~800kb DLL. but I don't have time to work 
> on it right 
> now, so this isn't really an issue.

Well, size is one aspect of 'lightweight', but startup speed is another one.
Rainer Keuchel notes that his build of Perl/Tk on WinCE is rather slow.
Obviously, he spend some efforts on profiling


> ,_PocketPC_Have_Serious_Design_Limitations which most often appears on
> devices with GSM radio stack, when many processes are always exist to
> support a phone.  

> I don't see how this one is related to PerlCE (more than any other WinCE 
> program, I mean). is there any special reason to consider this as a 
> problem for Perl?

you're right: this has nothing to do with Perl.
But I can't resist explaining when after upgrading to much more powerful
device I got much weaker Perl capabilities...


> > Another one is - probably latest patches to WinCE made some bad changes
and
> > now script often sporadically exits with a message "Exit code 14".
> > 
> > Probably my bad :(
> 
> well, right now I'm trying to run the whole perl test suite on my iPAQ. 
> should take quite a while, but, well, while I'm at the office the iPAQ 
> sits on its cradle doing nothing but sync most of the time; battery 
> time, at least, is not a problem :-)
> 
> I encountered some problems with @INC, but if I come up with something, 
> I will post the results and write an how-to for the wiki.
> 
> I hope that running the test suite should help isolate problems.

sounds very promising.

> 
> > When I did my changes, I sent patches to p5p. I think it is still
reasonable
> > to do same way. There's no WinCE pumpking.
> 
> but maybe a CVS repository on sourceforge could help, don't you think?

I will setup CVS this weekend, then.
If you will be kind to participate perlce project on SF - I'll give you all
permissions to that, just say me your user ID.

If development will have progress, then it will be reasonable to create
mailing list on perl.org: usually they create such lists quite quick.
(Mailing list for users of Tcl::Tk module was kindly created within a day!)

Best regards,
Vadim.