On 08/11/01 06:22 -0600, Billy Patton wrote: > Brian Ingerson, > Subscribed to the inline mailing list but got no response. > Am I to assume list is dead or has no subscribers?
I have been quiet on the list for the last 3 months, while I figured out what I was going to do next in my life. Now that I've figured it out, I plan to jump right back into Inline. Good timing :) BTW, Neil and I just had a meeting with a reputable publisher yesterday about writing a book on Inline. Stay tuned. NOTE TO THE LIST: My apologies if I have not replied to your emails recently. I will be going through the backlog very soon. > > Questions : > 1. directory _Inline is created in your current > working directory when executing a script using Inline. > is this true? The _Inline/ directory will be searched for in about 5 well known places. If not found, it will be created in your current directory or the directory containing the script, if permissions allow. Otherwise a swift death will ensue. See the doc. > 2. If I distribute the script to run 5k+ jobs on the network > will it have to compile 5k+ times, or will it refer to > the one in local working directory. > Does it use only 1 directory ? It will recompile unless it can find a cached version in an appropriate _Inline/ directory. By using the DIRECTORY option, or the PERL_INLINE_DIRECTORY env variable, you should have enough control to make it work the way you want. > 3. If _Inline does not exist in my current directory, what > will happen if 10+ jobs are all trying to compile and output > to the same location, at the same time? > Will this cause failure in all jobs until a completed > _Inline directory exists? Give me a very specific scenario. Better yet try it yourself and report back to the list. Chances are that you can do what you need. > If the answers to the above questions are true, Inline needs > more work. It is not yet ready for use in mainstream computing. Well Inline *does* need more work IMO. It is only beta software. At least that's my *official* stance. Nonetheless, it has been used in mainstream production coding for over a year with surprisingly little complaint. BTW, You may want to consider turning your Inlined code into a module and distributing it to the machines that require it. Inline has rock solid support for this that is virtually identical to XS after installation. Cheers, Brian PS The Inline authors have a pretty commendable track record for fixing issues as they arise. Let us know (with examples of course) if you have any.
