Comments on: java2perl6api – Java to Perl 6 API translation – What, Why, and Whereto

By: TimBunce

TimBunce — Sat, 18 Sep 2010 10:42:42 +0000

There are many Perl6 compiler projects (http://perl6.org/compilers/) but none that I know of target the JVM. I’m sure that’ll happen one day though. If it does, then yes, it may be useful for one aspect of my particular needs (i.e., being able to use the JDBC test suite). It would certainly be another useful technology for bridging Java and Perl 6 in general.

By: John Bokma

John Bokma — Fri, 17 Sep 2010 20:48:13 +0000

For a time I have been wondering how hard it is to compile Perl 6 to Java byte code. Since I guess that this would make what you want a bit easier?

By: TimBunce

TimBunce — Thu, 29 Jul 2010 19:49:31 +0000

Yes, and that's exactly the role DBDI will play in the Perl 6 world. There has to be a common API on which the higher-level ones build and below which the drivers are implemented.

By: Dolmen

Dolmen — Thu, 29 Jul 2010 14:20:44 +0000

JDBC is now a low-level API in the Java world. Most J2EE developers are forbidden to use it directly. Instead they must use ORM wrappers such as Hibernate.

By: Reasons Why Perl Isn’t Dead Yet | Ask Rea Maor (dot) Com - Technology and Money Making at its best

Tue, 27 Jul 2010 15:10:41 +0000

[...] They’re launching a project to translate the Java API to Perl 6. Which basically means that Perl will inherit a lot of Java’s leftover mojo. To hear people [...]

By: TimBunce

TimBunce — Sun, 18 Jul 2010 09:25:50 +0000

I’ll happily take a patch to add an option to generate dashed-methods. I don’t think I’d use it for the DBDI API though.

By: Nigel Hamilton

Nigel Hamilton — Sat, 17 Jul 2010 19:28:03 +0000

And dashed-methods-to-please

By: TimBunce

TimBunce — Fri, 16 Jul 2010 19:34:03 +0000

Let me say again, the DBDI API, based on JDBC, is for the *internal* interface between any future DBI and the drivers. It’s a foundation. It’s internal. It’s not what end users or CPAN modules would use.

By: Burak Gürsoy

Burak Gürsoy — Fri, 16 Jul 2010 19:25:05 +0000

I second that named parameters request (and no camelcase please).

By: Dave Rolsky

Dave Rolsky — Fri, 16 Jul 2010 17:26:07 +0000

Looking at the JDBC API, I can’t say I’m very excited about this. While it’s obviously battle-tested, it also makes some of the same mistakes (IMO) that DBI does.

The first thing that jumps out is the use of connection *strings*, rather than a structure. If I never write “dbi:Foo:dbname=bar;flurble=42″ again, it will be too soon. Please, please, please, let’s have named params. Perl 6 provides fabulous support for named & typed parameters. Let’s take advantage of that.

Do we really need CPAN6 to have 10 libraries all of which work around this backwards interface? Because it sure as hell will, if Perl 5 is anything to go by.

Also, the studlyCaps names just don’t seem very Perlish. Yes, it’ll be comfortable for Java developers, but I think the first audience for Perl 6 will be Perl 5 developers, and those names make my skin crawl.