[EMAIL PROTECTED]: # Sorry to disrupt your discussion with some loosely related # question... Could anyone help me determine which development # tools/IDEs are to be used when hacking at Parrot?
Whatever strikes your fancy. You could even use ed if you wanted to--although I wouldn't recommend it. :^) As long as it reads and writes ASCII and doesn't mangle the files, it's okay to use. # As you'd have guessed it, I'm relatively new to this project... # ;-). However, I do want to help out with the effort # to code a great 'system' that any other developer could # benefit from (including myself :). Welcome to the team then. :^) # Say, at home, I'm working on a Windows (ME) system. The IDEs # I have at my disposal are the MS Visual Studio (C++), CodeWarrior, # and some old DOS based C compilers. I've got CVS all set up on my # side so retrieving recent copy of the working files from the # Parrot cvs root shouldn't be of a problem. I'm also thinking # of moving to a Unix based system in a short while (since I've used # to coding on a Solaris box at work). I'm also on Win32 (Win2000, to be exact). I use WinCVS with two directories: parrot and parrot-cvs. parrot is my working copy and parrot-cvs is what's currently on CVS. I use Visual Studio.NET beta 2 ($13 from MS) as my editor, since ActiveState has a nifty Perl code editor plugin for it, and most of my work (I mostly muck with Configure, but wade into the C once in a while) is with Perl code. The actual directory structure looks like this: +--+ Perl 6 | +--+ parrot | | +--- .vcproj and related files | | +--+ parrot | | +--- working copy of CVS files | | | +--+ parrot-cvs | | +--+ parrot | | +--- pure copy of CVS files | | | +--+ babyperl | | +--- files related to babyperl | | | +--+ smoke | | +--- remote smoke-testing stuff I use PPT (Perl Power Tools--look around on the CPAN) to get various Unix utilities (although I haven't gotten their patch program to work well, diff works okay--I just apply patches via an SSH connection to a BSD box). Of course, you may choose a different solution than my cobbled-together collection of free and nonfree software--I've heard Cygwin works well for this sort of thing. Whatever tools you use, make sure you have fun working on Parrot. That is, after all, what it's all about. --Brent Dax [EMAIL PROTECTED] Configure pumpking for Perl 6 They *will* pay for what they've done.
