Yes, but then we'll run into a lot of DBD problems. What DBDs to we include? Can't include all, as they won't compile without clients, etc...
Now, remember, we are DBI users/lovers, etc... There is a whole different world out there that might not use RDBMS or any DB facilities, and they won't need nor want the DBI/DBD inclusion in core. Also remember that DBI/DBD updates are far more frequent than that of Perl, therefore how do we manage that. I personally prefer the grouped SDK idea. DBMS group, XML group, etc... Ilya -----Original Message----- From: Jeff Zucker To: [EMAIL PROTECTED] Cc: Simon Oliver; [EMAIL PROTECTED] Sent: 6/11/02 10:05 AM Subject: Re: Perl SDK? Tim Bunce wrote: > I think the Software Development Kit (SDK) approach has more appeal: > Define a standard bundle of extra modules that people are recommended > to install with Perl. Personally, I prefer the include-in-core approach because 1) Isn't all of perl an SDK? It's kind of like saying "click here to download perl to develop software and then click over there to download perl to develop software". 2) I think Simon's vison of "a guaranteed DBMS implementation on all platforms" makes a lot of sense. -- Jeff
