then I believe the best solution (that's been discussed thus far) is probably mine: to create a "library" folder full of files that you can selectively "include" in your programs. While the answer about creating "use"-type includes is nice (and certainly handy!), it may be a bit advanced for some. I've programmed on a professional basis for 6 1/2 years and have used the "library" method -- it's always worked well for me. I like to keep things as simple and straight-forward as possible so that just about anyone with at least a basic set of Perl skills could understand it. I would guess that I really only know about 100 commands in Perl (and that may be over-stating it) - but being able to put those commands together in a useful manner is what has given me a lucrative career as a Perl and MySQL programmer for the last several years! -Jimmy James
Hytham Shehab wrote: > i think that writing a module is not my answere, i think it is a huge > complicated answere for a simple question. > all what i want is simply put all my used subroutines in a seperate files, > then call the subroutine from that file whenever i want to use the > subroutine, am i clear now? > no redundency is my only target, thats it... > > thx v. much, specially Lundeen and drieux > > -- > Hytham Shehab > > -- > To unsubscribe, e-mail: [EMAIL PROTECTED] > For additional commands, e-mail: [EMAIL PROTECTED] -- To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
