develooper Front page | perl.perl5.porters | Postings from November 2011

RE: Autoloading charnames

Thread Previous | Thread Next
November 24, 2011 06:32
RE: Autoloading charnames
Message ID:
> From: Leon Timmermans
> On Thu, Nov 24, 2011 at 2:35 PM, Konovalov, Vadim wrote:
> > It is well-known adviced practice to use heavy "use something"
> > before any threads creation.
> >
> > I am just wondered, this automated
> >  use charnames; # :full or whatever
> > - will it be done before threads creation, or at what 
> moment it will be
> > called WRT threads?
> I assume it'd be done during compile-time, so it shouldn't matter.


As long as you know better, I can rely on this knowledge.

> > Have you seen how modules dependency in PAR resolved?
> >
> > There is some heuristic with false positives, and mostly 
> the logic is to
> > package more modules than needed, to avoid any misses in packed
> > executables, so resulting in bigger executables than needed.
> No, but I don't think that avoiding PAR bugs should be a guiding
> principle in perl's core design.

Look at this from the other side.

If perl this much full of such sudden behaviours,
it is much less maintainable.

Some of my application had only "perl.dll" with tiny scripts inside 
char [] strings.

The further we go, the harder perl servers as scalable embeddable helper engine.
It will be always huge and never tiny.

So - it is not PAR bugs that bother me, but uncontrollable behaviour.

> > But with proposed new feature things will end up with adding
> > "use charnames;" to all PAR-packed executables, thus resulting
> > already oversized executables to be even bigger.
> Then PAR/Module::ScanDeps needs to add detection for \N{}.

That's not realistic.

this is why I want for better control.
Ask what you want and you will get it.

This simple.

Thread Previous | Thread Next Perl Programming lists via nntp and http.
Comments to Ask Bjørn Hansen at | Group listing | About