Return-Path: <khera@kciLink.com>
Mailing-List: contact dev-help@perl.apache.org; run by ezmlm
Delivered-To: mailing list dev@perl.apache.org
Received: (qmail 15701 invoked from network); 5 Mar 2001 17:57:04 -0000
Received: from yertle.kcilink.com (postfix@208.184.13.195)
  by h31.sny.collab.net with SMTP; 5 Mar 2001 17:57:04 -0000
Received: by yertle.kciLink.com (Postfix, from userid 100)
	id 792DE2E443; Mon,  5 Mar 2001 12:57:01 -0500 (EST)
From: Vivek Khera <khera@kciLink.com>
MIME-Version: 1.0
Content-Type: text/plain; charset=us-ascii
Content-Transfer-Encoding: 7bit
Message-ID: <15011.54125.406264.160807@yertle.kciLink.com>
Date: Mon, 5 Mar 2001 12:57:01 -0500
To: "modperl-2.0 dev-list" <dev@perl.apache.org>
Subject: Re: Inline.pm and the future of XS
In-Reply-To: <Pine.LNX.4.30.0103052222390.29944-100000@llp.extropia.com>
References: <Pine.LNX.4.21.0103051046560.1422-100000@jack.sergeant.org>
	<Pine.LNX.4.30.0103052222390.29944-100000@llp.extropia.com>
X-Mailer: VM 6.90 under 21.1 (patch 14) "Cuyahoga Valley" XEmacs Lucid
X-Spam-Rating: h31.sny.collab.net 1.6.2 0/1000/N

>>>>> "SB" == Stas Bekman <stas@stason.org> writes:

SB> some new library comes out tomorrow, it takes probably minutes to write
SB> the glue.

SB> Of course it'll take the same time to do the same for XS gurus, but
SB> remember that many aren't.

The first time I had to make a Perl binding for a C library, it took
me about 2 hours to figure out how to do it.  Using XS to bind Perl
directly to a C API is trivial.  Making it perl-ish is the hard part.