Messages in this thread | | | Date | Sat, 1 Feb 2003 01:05:20 +0100 | From | "J.A. Magallon" <> | Subject | Re: Perl in the toolchain |
| |
On 2003.02.01 Roman Zippel wrote: > Hi, > > On Sat, 1 Feb 2003, J.A. Magallon wrote: > > > The easies way (from my point of view): write Perl::KConfig in C to do the logic > > hard work and build the big thing in perl. That will be putting a perl > > interface on top of klibc ? > > You gain _nothing_ by rewritting it in perl. The backend is already a > library and a swig interface file exists, so it's already trivial to > generate Perl::KConfig. There is absolutely no reason to force people to > use perl. >
No, that was exactly what I tried to say, take nowadays C library, and build a loadable module for perl (it has not to be written in perl).
-- J.A. Magallon <jamagallon@able.es> \ Software is like sex: werewolf.able.es \ It's better when it's free Mandrake Linux release 9.1 (Cooker) for i586 Linux 2.4.21-pre4-jam1 (gcc 3.2.1 (Mandrake Linux 9.1 3.2.1-5mdk)) - To unsubscribe from this list: send the line "unsubscribe linux-kernel" in the body of a message to majordomo@vger.kernel.org More majordomo info at http://vger.kernel.org/majordomo-info.html Please read the FAQ at http://www.tux.org/lkml/
| |