On Nov 29, 2007 7:45 AM, Alex Kapranoff <[EMAIL PROTECTED]> wrote:
> В Чтв, 29/11/2007 в 07:18 +0100, James Fuller пишет:
> > On Nov 28, 2007 8:46 PM, chromatic <[EMAIL PROTECTED]> wrote:
> > > On Wednesday 28 November 2007 10:59:30 James Fuller wrote:
> > > > I do not nec. agree with 'a particular
В Чтв, 29/11/2007 в 07:18 +0100, James Fuller пишет:
> On Nov 28, 2007 8:46 PM, chromatic <[EMAIL PROTECTED]> wrote:
> > On Wednesday 28 November 2007 10:59:30 James Fuller wrote:
> > > I do not nec. agree with 'a particular grammer is not' part of the
> > > core ... if that grammar is so common to
On Wed, Nov 14, 2007 at 08:09:31PM -0600, Jonathan Scott Duff wrote:
: On Nov 14, 2007 2:47 PM, Nicholas Clark <[EMAIL PROTECTED]> wrote:
:
: > On Sat, Sep 08, 2007 at 01:48:39PM +0100, Nicholas Clark wrote:
: > > Have I got this correct?
: > >
: > > state @a = foo(); # Implicit START block ar
On Nov 28, 2007 8:48 PM, Geoffrey Broadwell <[EMAIL PROTECTED]> wrote:
> On Wed, 2007-11-28 at 19:59 +0100, James Fuller wrote:
> > XML Parser is what I am talking about
>
> OK -- do you want an event-based parser? Do you want a DOM parser? Do
> you want a simplified tree generator parser? Do yo
On Nov 28, 2007 8:46 PM, chromatic <[EMAIL PROTECTED]> wrote:
> On Wednesday 28 November 2007 10:59:30 James Fuller wrote:
>
> > I do not nec. agree with 'a particular grammer is not' part of the
> > core ... if that grammar is so common to every problem (like regex is)
> > then why not include it?
At 6:06 PM +0100 11/28/07, James Fuller wrote:
there seems to be a dearth of xml 'ness' in Perl 6 design ... perhaps
before Perl 6 is fully baked its time to review what could live in the
core versus an external module.
thoughts?
cheers, Jim Fuller
I want to state agreement with others that thi
On Wed, 2007-11-28 at 18:12 +, Nicholas Clark wrote:
> On Wed, Nov 28, 2007 at 06:06:14PM +0100, James Fuller wrote:
> > there seems to be a dearth of xml 'ness' in Perl 6 design ... perhaps
> > before Perl 6 is fully baked its time to review what could live in the
> > core versus an external m
On Wed, 2007-11-28 at 11:46 -0800, chromatic wrote:
> The criterion for including a module in the core is "Is this necessary to get
> and install other modules?" not "Why not include this module?"
WELL SAID.
-'f
On Wed, 2007-11-28 at 19:59 +0100, James Fuller wrote:
> XML Parser is what I am talking about
OK -- do you want an event-based parser? Do you want a DOM parser? Do
you want a simplified tree generator parser? Do you care about memory
limitations? Run time?
Does the parser need to be robust a
On Wednesday 28 November 2007 10:59:30 James Fuller wrote:
> I do not nec. agree with 'a particular grammer is not' part of the
> core ... if that grammar is so common to every problem (like regex is)
> then why not include it?
Because it's not necessary for getting and installing other extension
On Wed, Nov 28, 2007 at 07:42:29PM +0100, James Fuller wrote:
> in the meantime, I have yet to get latest trunk perl6 running
> properly, on parrot, or freebsd then I will start thinking of such a
> task (everything compiles fine). as an aside I am getting an;
>
> "load_bytecode" couldn't find fi
On Nov 28, 2007 7:50 PM, Geoffrey Broadwell <[EMAIL PROTECTED]> wrote:
> Not too put too strong a bias on it, but:
>
> XML processors are a dime a dozen. There is no way for us to know *now*
> what the "best" XML processor(s) will be a decade from now, and Perl 6
> is intended to be a very long te
On Nov 28, 2007 7:39 PM, Andy Armstrong <[EMAIL PROTECTED]> wrote:
> On 28 Nov 2007, at 18:28, James Fuller wrote:
>
> > A few things I could imagine; native XML data type (and whatever that
> > means at this late stage)
>
> What might that mean at any stage?
from a syntactic point of view, h
Not too put too strong a bias on it, but:
XML processors are a dime a dozen. There is no way for us to know *now*
what the "best" XML processor(s) will be a decade from now, and Perl 6
is intended to be a very long term language. And frankly there are
enough different use cases to ensure that no
On Nov 28, 2007 7:31 PM, C.J. Adams-Collier <[EMAIL PROTECTED]> wrote:
> On Wed, 2007-11-28 at 18:12 +, Nicholas Clark wrote:
> > On Wed, Nov 28, 2007 at 06:06:14PM +0100, James Fuller wrote:
> > > there seems to be a dearth of xml 'ness' in Perl 6 design ... perhaps
> > > before Perl 6 is full
On 28 Nov 2007, at 18:28, James Fuller wrote:
A few things I could imagine; native XML data type (and whatever that
means at this late stage)
What might that mean at any stage?
--
Andy Armstrong, Hexten
all makes good sense,
to make a poor analogy (and to make my point);
the java build tool, Apache Ant went through the same sort of cycle
(at a much smaller scale) whereby initial architecture forced a lot of
extraneous functionality into the core hard to maintain and
limited deployment profi
On Wed, Nov 28, 2007 at 06:06:14PM +0100, James Fuller wrote:
> there seems to be a dearth of xml 'ness' in Perl 6 design ... perhaps
> before Perl 6 is fully baked its time to review what could live in the
> core versus an external module.
>
> thoughts?
If I remember the plan correctly, it's rou
there seems to be a dearth of xml 'ness' in Perl 6 design ... perhaps
before Perl 6 is fully baked its time to review what could live in the
core versus an external module.
thoughts?
cheers, Jim Fuller
19 matches
Mail list logo
