Thanks for the replies. I will look forward to it.
On Thu, Mar 5, 2009 at 6:20 AM, Reini Urban <[email protected]> wrote: > 2009/3/4 tuxdna <[email protected]>: > > I have two queries. > > > > * command line parameters > > > > Unlike gdb and perl -d, parrot_debugger always require a file name to be > > passed as command line parameter. Even though there is an option to load > a > > file once we launch the parrot_debugger using "load" command. > > > > Should we make the file name optional in the command line parameters lile > > gdb and perl -d have ? > > Sure, why not. > > > * getopt() - unistd.h > > > > I see that in src/parrot_debugger.c, the command line options are being > > parsed using argv pointers directly. > > > > Can we use getopt() of unistd.h to parse command line arguments in > > src/parrot_debugger.c or is there any portability issue with this? > > See the other pbc utils. We use our own include/parrot/longopt.h > > Create a ticket in trac and attach a patch. > > readline integration is also missing. > t/tools/parrot_debugger.t is also very incomplete >
_______________________________________________ http://lists.parrot.org/mailman/listinfo/parrot-dev
