On 17/11/05 11:30 -0800, Ira Woodhead wrote: > For number 3: > > There is an incompatibility with the current default "h2xs -XA -n ModuleName" > module layout. The .pm files now go into a lib/ dir, which inline can't seem > to figure out. > > My workaround is to just put the .pm file in the top level as before.
That's a very good point. Inline must understand the lib stuff. I remember it being tricky... But this time around I am going to focus a little bit differently. Inline is magical, but I think it needs to not be *overly* magical. For instance, I wanted Inline 0.50 to have a magic that would autobundle Inline.pm for systems that didn't have inline. But the better solution is just to require Inline. It's not that big of a deal. And with Module::Install you can still autobundle if you wanted to. I'll also be sure to write more tests. :) Cheers, Ingy > > > > -----Original Message----- > From: Ingy dot Net [mailto:[EMAIL PROTECTED] > Sent: Thursday, November 17, 2005 11:20 AM > To: inline@perl.org > Subject: Inline 0.45 > > > Hi All, > > I'm thinking about releasing a new version of Inline in the next two months. > > The focus would be this: > > 1) Separate Inline::C into a separate distribution. > 2) Make it easy to write C extension modules with Inline. > 3) Fix any bugs that have accumulated in the last 3 years. > > I think I can handle the first two, although suggestions are welcome. Any > specific things I should be thinking about for number 3? > > Cheers, Brian > > > > ----------------------------------------------------------------------------------- > ATTENTION: DO NOT read, copy or disseminate this communication unless you are > the intended addressee. This message and any file(s) or attachment(s) > transmitted with it are confidential, intended only for the named recipient, > and may contain information that is a trade secret, proprietary, protected by > the attorney work product doctrine, subject to the attorney-client privilege, > or is otherwise protected against unauthorized use or disclosure. This > message and any file(s) or attachment(s) transmitted with it are transmitted > based on a reasonable expectation of privacy consistent with ABA Formal > Opinion No. 99-413. If you have received this communication in error, please > e-mail the sender and notify the sender immediately that you have received > the communication in error. Thank you.
