Hi all, I get the feeling this is getting quite serious. If we are going to cooperate on this, I propose that we do it seriously to avoid having 3 people doing the same thing in incompatible ways.
Can some one lead this? What is it we want to do and with what ? I can see at least 1 big problem (which is a little in fact), NAMING. I have an Inline::Flex and an Inline::Bison in alpha. To me Inline::SomeToolOrLanguage is a direct mapping to the language or tool with the added possibility to map the tools output to perl. As an example Jochen's Inline::Yacc modifies the way one writes yacc grammar as they are enhanced to allow direct perl (or other language) coding in the grammar. I think this (the naming of the module) is counter intuitive. Add to this that writing 20 lines of perl code in a grammar instead of just calling a sub (that would be in the normal perl part) seems even more counter intuitive. I am not complaining about jochen's module, I think the idea is great. Can someone (Ingy?) take responsibility over all naming. What I have in my pocket is: Inline::Flex direct mapping (exports yylex only) Inline::Bison Inline::Byacc All this modules are direct mapping, nothing fancy. I am ready to rename them to whatever as long as we all agree. This weekend I will look at jochen's module. -----Original Message----- From: Brian Ingerson [mailto:[EMAIL PROTECTED]] Sent: Saturday, December 08, 2001 2:31 AM To: Nadim Khemir Cc: [EMAIL PROTECTED] Subject: Re: Inline not viable with this speed Revamped by nadim. > Problems : > There is a big problem with inline, SPEED. The main problem is the use of Parse::Recdescent. > I timed the inlining process to 1:40 > > dprofpp.bat -O 50 Yow! I had no idea P::RD was such a pig. Thanks for this data. It's proof enough. Let me step back a second and wax philosophical... Inline's primary usage is to *bind* languages to Perl. I've stated this before, but I'll do it again. On a large project, one should build a separate object out of most of the code, and only Inline the code needed to create the Perl bindings. In other words, if a C function isn't intended to be called by Perl directly, it probably shouldn't be Inline. This makes sense from a code maintenance point of view as well. So in practice the Inline C code stays rather small, and thus the compile times are generally acceptable. NOTE: The longest compile time I ever had was 45 seconds. That was on a P266 running Windows on top of Vmware! I've never seen more than 3-4 seconds other than that case. I never see these 3-4 seconds. And I test on 2 machines. That said, Ingy is not one to set arbitrary limits upon those who use his software. (He merely guides...) Parse::RecDescent is a *proven* hog. Let's replace it! 5) Neil and I have always wished to implement the Inline::C parser using cc, or whatever the native compiler happened to be. Then we'd use nm to dump the symbols and just parse that. Although it's a "science project" to support every platform, think of the increase in speed and accuracy. Now we can easily offer this as an option. Or better yet someone else could take this on :) Inline::C::NativeUnixParse... Oh yes this is a good idea, a killer one even. I like it and will look at this one. So Neil and I have decided to release a new minor (well, semimajor) version of Inline.pm (0.44) for Christmas. (And yes, we mean 2001) This will probably include: - Fixes for most bugs reported since 0.43 Interesting where are the bugs kept. - Support for alternate parsers :) - Better debugging output - A rudimentary Inline shell. (insh) - Think of it as a terminal based Inline IDE - Neil has become a Perl shell writing whiz. Check out ActiveState's new ppm3 installer. It's killer! - Will eventually work with all Inline::* modules If you have any urgent needs for the release, please speak up now. The next planned release will be the famed 0.50 (halfway point :) and will probably come out in mid winter. Please realease it before the 21st we have a longer holidays in Sweden. And the bears bite all the aerial cable use for Internet and telephone in my house in the woods of smaland. Nadim. (The bears are a joke of course, it almost never snows where I live)
