Re^2: Will the real Internals module please stand up?

They could have been included in the module, the same way that there are utility functions in the charnames pragma that you can load without triggering the pragma behavior via "use charnames ()" or "require charnames".

So either it was just a "speedier alternative", as you say, or it was desired that the module not need to be loaded. I can't guess which.

--
Online Fortune Cookie Search
Office Space merchandise

Comment on Re^2: Will the real Internals module please stand up?

Replies are listed 'Best First'.
Re^3: Will the real Internals module please stand up? by demerphq (Chancellor) on Nov 16, 2012 at 11:00 UTC
One reason to put things in universal.c is it allows you to use these functions in miniperl. If they are used by things that are run by miniperl or they are used to test perl then they need to be available early. Another reason is that functions are used to implement parts of perls internals, and therefore need to be around. An example is some of the re:: routines that are used to implement named captures. They need to be usable without loading the re dll, which also contains a full debugging enabled version of the regex engine. --- $world=~s/war/peace/g	[reply]

Replies are listed 'Best First'.

Re^3: Will the real Internals module please stand up?
by demerphq (Chancellor) on Nov 16, 2012 at 11:00 UTC

One reason to put things in universal.c is it allows you to use these functions in miniperl. If they are used by things that are run by miniperl or they are used to test perl then they need to be available early. Another reason is that functions are used to implement parts of perls internals, and therefore need to be around. An example is some of the re:: routines that are used to implement named captures. They need to be usable without loading the re dll, which also contains a full debugging enabled version of the regex engine.

---
$world=~s/war/peace/g

[reply]