I would agree with you if the only purpose of do would be to "load subroutines and initialization code at runtime" in a similar way as require does, but for those (rare?) cases this should be done repeatedly. However, from my understanding of do, this function is much more general: It is, in spirit, much more like eval, only that the evaluated code resides in a file, not in a string or block. This can, IMO, not only seen from the description of do, but also from the fact that $@ is set after an exception. We wouldn't place the requirment, that code evaluated by eval should return a true value unless it fails, do we? I, personally, would say that the same applies to do.
Maybe our different views in that matters come from the fact that I'm using do in a different way. We are using it to inject (for purpose of debugging) arbitrary code at specific "hook point" in a running application.
In reply to Re^6: Why do we need a \n with do FILENAME?
by rovf
in thread Why do we need a \n with do FILENAME?
by rovf
| For: | Use: | ||
| & | & | ||
| < | < | ||
| > | > | ||
| [ | [ | ||
| ] | ] |