Re: [svn:perl6-synopsis] r14317 - doc/trunk/design/syn

[Andreas J. Koenig]

$spot:Inconsistent:(parens)

 On Wed,  7 Mar 2007 20:38:17 -0800 (PST), [EMAIL PROTECTED] said:

   +class Dog:ver1.2.1:authcpan:JRANDOM;
   +class Dog:ver1.2.1:authhttp://www.some.com/~jrandom;
   +class Dog:ver1.2.1:authmailto:[EMAIL PROTECTED];
   +class Dog:1.2.1 cpan:JRANDOM

   +class Pooch:nameDog:ver1.2.1:authcpan:JRANDOM
   +class Pooch:Dog 1.2.1 cpan:JRANDOM

So far you're using angle brackets

   -use Dog-(Any)-(Any);
   +use Dog:ver(Any):auth(Any);

From here you start mixing angle brackets and parens.
 
   -use Dog-1.2.1;
   +use Dog:1.2.1;
 
   -use Dog-1.2.1-(Any);
   +use Dog:ver1.2.1:auth(Any);

Even in one line.
 
   -use Dog-(1.2.1..1.2.3);
   -use Dog-(1.2.1..^1.3);
   -use Dog-(1.2.1..*);
   +use Dog:ver(1.2.1..1.2.3);
   +use Dog:ver(1.2.1..^1.3);
   +use Dog:ver(1.2.1..*);
 
   +use Dog:ver(1.2.1 | 1.3.4):auth(/:i jrandom/);
   +use Dog:ver(Any):auth({ .substr(0,5) eq 'cpan:'})
 
   -use Perl-(v6..*)-(Any);
   +use Perl:ver(v6..*):auth(Any);
 
Seems accidentally to me.

-- 
andreas

Re: [svn:perl6-synopsis] r14317 - doc/trunk/design/syn

[Andreas J. Koenig]

 On Thu, 08 Mar 2007 07:21:19 +0100, [EMAIL PROTECTED] (Andreas J. Koenig) 
 said:

   $spot:Inconsistent:(parens)

Please accept my apologies for my ignorant posting. Clearly the parens
indicate ranges. Sorry for the noise.

Going back into lurker-mode,
-- 
andreas

Re: Why shouldn't sleep(0.5) DWIM?

[Andreas J. Koenig]

 On Wed, 31 Jan 2001 12:04:46 +, Nicholas Clark [EMAIL PROTECTED] said:

 dbmopen() already loads AnyDBM_File to do the real work without the
 user (or script) knowing, so this idea could be extended.

And nobody in this thread has ever mentioned Time::HiRes. Is there a reason?

-- 
andreas

Re: RFC on Coexistance and simulaneous use of multiple module version s?

[Andreas J. Koenig]

 On Fri, 26 Jan 2001 16:37:23 -0500, Michael G Schwern [EMAIL PROTECTED] said:

  from what I remember we discussed
  an idea to allow people and organizations to produce their own list of
  approved modules.

This is already possible with the CPAN::Site module.

  For example, if Oracle had their own QA people
  approve a set of modules and versions allowed for use in their
  company.  These lists would be archived and made available just like
  CPAN is now.  A subclass of the CPAN shell could be built allowing the
  user to specify which organizations they trust and it would only pull
  modules from there.

This description goes a bit beyond CPAN::Site's abilities.

  This isn't *quite* what most people are thinking of, and it in no way
  addresses the problem of having multiple versions of the same module
  installed on a given machine, but it does allow people to pick and
  choose between implementations without fragmenting CPAN.

Larry mumbled something like "implements" and "interface". So to say

package Net::FTP::Foo implements Net::FTP;

But I don't think, anybody wrote an RFC about the plan.

-- 
andreas