Re: [Parseperl-discuss] My dev plans

[Chris D. <ch...@ch...>]

On Sep 22, 2006, at 12:06 AM, Adam Kennedy wrote:

> Audrey had the right idea.
>
> Instead of having a ->base or whatever, we should be subclassing  
> Number into a set of subclasses, one for each type of number Perl  
> supports.
>
> So Number::Boolean, Number::Hexidecimal, Number::Unicode etc
>
> So ignoring the parsing half, I'd start by setting up the  
> subclasses, and then look at how the implementation we need fits  
> into that model.

Excellent.  That sounds like a good approach to me.  But I don't know  
what Number::Unicode means...  Also, should there be a  
Number::Decimal, or should that just be Number.pm?

> But I'm pretty excited about this, since I've wanted it done for ages.
>
> And with ->literal working at the Number level, it's fairly easy to  
> start pushing it upwards, add support for strings, and anonymous  
> hashref constructors and so on, until we can handle any arbitrarily  
> deeply nested thing, so long as it is all literals with no need to  
> resort to the Perl interpreter (and thus avoid the Halting Problem  
> issues).
>
> Are you planning on branching SVN for this? Or should we just  
> release 1.118 and then you can hack away at the trunk. (I'm cool  
> with either)

Trunk, I think.  I'm an intermittent hacker ($kid and $job), so a  
branch would probably just bitrot.  My "short term" means about a month.

In any case, my first task will be test coverage, as I said before.   
I want to get the current stuff debugged before adding new features.

Chris

P.S.
   Is "hexidecimal" some odd aussie spelling for hexadecimal?  :-P
   I inferred from the POD today that it pains you to spell  
"tokeniser"/"tokenizer"!
   I tried really hard not to americanize the spelling all over the  
POD this morning...

--
Chris Dolan, Software Developer, http://www.chrisdolan.net/
Public key: http://www.chrisdolan.net/public.key
vCard: http://www.chrisdolan.net/ChrisDolan.vcf