That's not the problem. The problem is how do you deal with multi-language dependencies in the requires: (et al) parts of the META.yml.
Adam K On Fri, Apr 16, 2010 at 10:17 AM, Ævar Arnfjörð Bjarmason <ava...@gmail.com> wrote: > On Fri, Apr 16, 2010 at 00:07, Adam Kennedy <a...@ali.as> wrote: >> The complexity of a multi-language META specification (and I've >> actually written one as an experiment in the past) requires a >> something other than (and bigger than) META.yml > > All you need to support any language is to: > > 1. Allow language => or something like it > 2. Allow extensions to the format. META 2.0 does this via its X_* keys. > > Before ^1 was removed from the spec I couldn't think of a language > that couldn't be shoe-horned into it with some custom X_* keys. Even > without ^1 it can still be hacked in by just requiring version X of > "some_module_name_that_is_a_language". It's just more hacky. > > Perl 6's idea of modules isn't finalized. But meanwhile something like this: > > class Dog:auth<mailto:jran...@some.com>:ver<1.2.1>; > > Can be expressed in META.yml like this: > > X_auth => { mailto => 'jran...@some.com' }, > X_ver => '1.2.1', > > etc. Can you think of anything that can't be supported like this and a > custom indexer that reads the magic X_* values? >
