G'day ghosh123,

In the use documentation, you'll see:

It is exactly equivalent to

BEGIN { require Module; Module->import( LIST ); }
[download]

except that Module must be a bareword. The importation can be made conditional by using the if module.

So, if you had to use require, you could still get the compile time checks with:

BEGIN { require Module; }
[download]

However, reading a bit further down the use documentation, you'll see that this is exactly equivalent to

use Module ();
[download]

So, unless you're unable to specify a bareword for Module (see this post of mine from a few days ago for an example), or you have a particular need to load Module at runtime (e.g. your point #4 scenario [although see below]), there's really no reason not to use use.

Finally, regarding the points you made:

1. Correct.
2. Correct.
3. The "control is passed to that file at run-time" part doesn't sound right at all. If, after reading the documentation I've provided links to, you still believe this is correct, please clarify what you mean (perhaps I'm missing your intent).
4. In that particular scenario, you'd probably need to weigh up whether you want to avoid an initialisation delay at the expense of (conditionally) having the same delay at some point in the middle of the program. There are situations where modules are loaded conditionally, using require, that have nothing to do with initialisation delays (as an example, see the File::Spec source code).