[prev in list] [next in list] [prev in thread] [next in thread] 

List:       perl6-internals
Subject:    [perl #46503] [DEPRECATED] Remove individual runcore command line
From:       "Will Coleda via RT" <parrotbug-followup () parrotcode ! org>
Date:       2009-02-28 5:15:44
Message-ID: rt-3.6.HEAD-21965-1235798143-135.46503-15-0 () perl ! org
[Download RAW message or body]

(Reposting to cc list; look for my embedded comment.)

On Fri Feb 27 21:13:30 2009, coke wrote:
> On Fri Oct 19 17:20:38 2007, particle wrote:
> > i've added -R, --runcore options to parrot in r22284, with
> documentation
> > and tests. see C<parrot --help> and C<perldoc docs/running.pod> for
> details.
> >
> > next we need to decide what to do about the old options. when do we
> > deprecate them? how do we migrate to the new syntax? etc. if you
> have
> > ideas, let them be known by replying here.
> >
> > i suggest we migrate all existing code to the new options at once,
> 
> This part never happened. =-)
> 
> I have a patch nearly ready to go to rip these out, but am having a
> problem with t/harness ;
> there is code to make "-b" convert to "--runcore=bounds", but it seems
> broken:
> 
> If I deliberately put an error in one of the test files, I can see:
> $ make testb
> <SNIP>
> ./parrot -b -D40 --gc-debug -O1
> --output=t/compilers/imcc/imcpasm/cfg_1.pasm
> 
> Once "t/harness -b" passes the right option to parrot, I can run a
> fulltest and then commit
> my patch.
> 
> Hopefully this is a simple perl task for someone to tackle.
> 
> > and
> > mark the old options as deprecated. however, i'd like to see the old
> > options stay around for a while, perhaps with a runtime warning
> after
> > the 0.5.0 release, a fatal error after 0.6.0, and removal in 0.7.0.
> > those  last two release numbers are flexible.
> >
> > your thoughts?
> > ~jerry


-- 
Will "Coke" Coleda
_______________________________________________
http://lists.parrot.org/mailman/listinfo/parrot-dev
[prev in list] [next in list] [prev in thread] [next in thread]