According to the document: "It is very important that function definition files only contain the definition for the specified function and nothing else. Otherwise, it is possible that autoloading a function files requires that the function already be loaded, which creates a circular dependency."
So an autoloading function file can only contain the definition of the specified function and nothing else. I'm not fully understand the reason in the document. But what if this specified function references to some other tool function, if I cannot put the tool function inside the same file, where should I put it? In the .load file? If I don't want to expose this tool function, I don't think it's a good idea to put it in .load file. Another question, similar to this one, if 2 autoloading function both calls to one tool function, and I want to expose this tool function too, seems the only way to do that, is to put this tool function into config.fish, which lost the benefits of autoloading function. Is it possible to make this tool function an autoloading function, and make other autoloading functions depend on it? Thanks, Leira Hua ------------------------------------------------------------------------------ November Webinars for C, C++, Fortran Developers Accelerate application performance with scalable programming models. Explore techniques for threading, error checking, porting, and tuning. Get the most from the latest Intel processors and coprocessors. See abstracts and register http://pubads.g.doubleclick.net/gampad/clk?id=60136231&iu=/4140/ostg.clktrk _______________________________________________ Fish-users mailing list Fish-users@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/fish-users
