[perl #55386] [RFC] Remove Configure.pl -miniparrot option

2008-11-23 Thread James Keenan via RT
Coke, notfound:

Did we reach any resolution on these questions?

Thank you very much.

kid51


Re: [perl #55386] [RFC] Remove Configure.pl -miniparrot option

2008-06-06 Thread NotFound
On Fri, Jun 6, 2008 at 6:15 AM, via RT Will Coleda
[EMAIL PROTECTED] wrote:

 I'm not sure that supporting this option (And having to fix bugs to do
 it) is worth it. If we can remove this, we can also remove anything in
 the code that is ifdef'd around MINIPARROT.

Several minipparot related tickets involve PIO inability to work with
FILE * handles, and I think no one is working on this issue because of
planned redoing of IO system using roles. So I think that we must
delay the decision until that work is done, maybe at that point all
fixes become trivial.

-- 
Salu2


[perl #55386] [RFC] Remove Configure.pl -miniparrot option

2008-06-05 Thread via RT
# New Ticket Created by  Will Coleda 
# Please include the string:  [perl #55386]
# in the subject line of all future correspondence about this issue. 
# URL: http://rt.perl.org/rt3/Ticket/Display.html?id=55386 


Configure.pl says:

   --miniparrot Build parrot assuming only pure ANSI C is available

To add confusion, the build following a normal config already
constructs a miniparrot on the way to building parrot, and I thought
we were targetting this level of C across the board?

We have several tickets that refer to errors when trying to build with
this option.

I know the eventual goal was to potentially build a smaller bird, and
then use it to construct the full-sized model, but I think we might be
better off cleaning house here; We've already pretty much agreed that
Perl is going to be a build requirement through 1.0, haven't we?

I'm not sure that supporting this option (And having to fix bugs to do
it) is worth it. If we can remove this, we can also remove anything in
the code that is ifdef'd around MINIPARROT.

Comments?

-- 
Will Coke Coleda