# New Ticket Created by  James Michael DuPont 
# Please include the string:  [perl #19874]
# in the subject line of all future correspondence about this issue. 
# <URL: http://rt.perl.org/rt2/Ticket/Display.html?id=19874 >


this is the patch to compile pdump under linux
basically it removes a field that was not used anymore

--- James Michael DuPont <[EMAIL PROTECTED]> wrote:
> From James Michael DuPont Sat Jan  4 08:22:46 2003
> Received: from [80.128.234.119] by web13302.mail.yahoo.com via HTTP;
> Sat, 04 Jan 2003 08:22:46 PST
> Date: Sat, 4 Jan 2003 08:22:46 -0800 (PST)
> From: James Michael DuPont <[EMAIL PROTECTED]>
> Subject: Re: Introduction and cygwin results
> To: Dan Sugalski <[EMAIL PROTECTED]>, [EMAIL PROTECTED]
> In-Reply-To: <a05200f25ba3c39098e79@[192.168.3.1]>
> MIME-Version: 1.0
> Content-Type: text/plain; charset=us-ascii
> Content-Length: 1284
> 
> 
> --- Dan Sugalski <[EMAIL PROTECTED]> wrote:
> > At 10:51 AM -0800 1/3/03, James Michael DuPont wrote:
> > >Can someone tell me if anyone uses packdump from cvs? is that an
> > >equivalent to ildasm in dotnet? It seems to be broken.
> > >Can I dump an set of instructions from a program into a file, and
> > >reassemble them?
> > >If not, is there a way to dump a parrot program?
> > 
> > Not that I know of, I think so, damn, you should be able to, and no
> 
> > no other way.
> 
> Here is my patch for pdump :
> But the pdump does not disassemble... i have to look into
> dissassemble.pl
> 
> Index: packdump.c
> ===================================================================
> RCS file: /cvs/public/parrot/packdump.c,v
> retrieving revision 1.6
> diff -u -r1.6 packdump.c
> --- packdump.c        2 Nov 2002 14:57:47 -0000       1.6
> +++ packdump.c        4 Jan 2003 16:18:37 -0000
> @@ -107,8 +107,13 @@
>  
>      case PFC_STRING:
>          PIO_printf(interpreter, "    [ 'PFC_STRING', {\n");
> -        PIO_printf(interpreter, "        FLAGS    => 0x%04lx,\n",
> +
> +        #ifdef HAS_parrot_string_t_flags
> +        
> +                PIO_printf(interpreter, "        FLAGS    =>
> 0x%04lx,\n",
>                     (long)self->string->flags);
> +        #endif 
> +
>          PIO_printf(interpreter, "        ENCODING => %s,\n",
>                     self->string->encoding->name);
>          PIO_printf(interpreter, "        TYPE     => %s,\n",
> 
> Anyone working on cross compiling? I have a setup here for cross
> compiling from debian to windows, but always use autoconf to do that.
> Anyone have an idea?
> 
> > 
> > >Is there a way to capture the line number, and comments of a perl6
> > >program in parrot? What about high level type information?
> > 
> > Line number, yes. Comments, probably not, though it's possible that
> 
> > info can get embedded. What type of high-level info are you looking
> 
> > for? We've all sorts. :)
> well as much as you can give me.
> 
> > Seriously, if you're looking for variable 
> > type info, it'll potentially be there, assuming that it's not been 
> > stripped out.
> 
> OK, that is good.
> 
> > 
> > >I would be willing to port my code to the subset of perl/parrot
> that
> > is
> > >currently supported, where I can i find that?
> > 
> > Perl 6 is in languages/perl6, though I think that there's still
> some 
> > stuff missing.
> Well, I will try that out. Thanks,
> 
> mike
> 
> =====
> James Michael DuPont
> http://introspector.sourceforge.net/
> 
> __________________________________________________
> Do you Yahoo!?
> Yahoo! Mail Plus - Powerful. Affordable. Sign up now.
> http://mailplus.yahoo.com
> 


=====
James Michael DuPont
http://introspector.sourceforge.net/

__________________________________________________
Do you Yahoo!?
Yahoo! Mail Plus - Powerful. Affordable. Sign up now.
http://mailplus.yahoo.com


Reply via email to