Re: Am I a part of this world ?
Brent 'Dax' Royal-Gordon
> I was wondering, whether I would just remain a mere
> spectator, or will I get an opportunity to do anything
> as well.
Hello Patrik,
Parrot isn't really an environment where people are *assigned* work;
they just do something that's necessary. If you're not sure what to
do...
* Documentation is always nice, and usually sorely lacking.
* Likewise with tests.
* The Parrot todo list is at <http://www.parrotcode.org/todo.html>.
Some of the items are more estoric than others.
* Dan Sugalski (the internals designer) will occasionally post a
"small task for the interested" to the list, which you could do. You
can search the archives for old ones and see if they've been done.
If you're using Windows, there are several todo items specifically for
that OS; fixing those would be helpful, since there aren't too many
Windows hackers here. If you're familiar with assembly language on a
processor other than the i386, the JIT people could use a hand. If
you know Python, there's a half-finished Python implementation you can
work on...just poke around and you'll find things.
HTH,
--
Brent 'Dax' Royal-Gordon <br...@brentdax.com>
Perl and Parrot hacker
There is no cabal.
[I currently have a couple Gmail invites--contact me if you're interested.]
Dan Sugalski
>Pratik Chandra Roy <prat...@yahoo.com> wrote:
>> I was wondering, whether I would just remain a mere
>> spectator, or will I get an opportunity to do anything
> > as well.
>
>that OS; fixing those would be helpful, since there aren't too many
>Windows hackers here.
Windows! Yeah, that'd be an amazing help. I went to go build parrot
on Oni over the weekend to see how it went. Failed under both cygwin
and VS/.NET, both because of ICU. (Cygwin was linking against a
nonexistent ICU library, and the VS/.NET makefile was looking for an
msdev executable to do something or other, but VS/.NET doesn't *have*
an msdev program shipped with it...)
--
Dan
--------------------------------------it's like this-------------------
Dan Sugalski even samurai
d...@sidhe.org have teddy bears and even
teddy bears get drunk
Matt Fowles
I definitely have to agree with that. If I could have this working on
VS/.NET (the free version), my level of contribution would probably go
up a fair amount...
Matt
On Tue, 12 Oct 2004 14:00:53 -0400, Dan Sugalski <d...@sidhe.org> wrote:
> At 10:47 AM -0700 10/12/04, Brent 'Dax' Royal-Gordon wrote:
> >Pratik Chandra Roy <prat...@yahoo.com> wrote:
> >> I was wondering, whether I would just remain a mere
> >> spectator, or will I get an opportunity to do anything
> > > as well.
> >
> >If you're using Windows, there are several todo items specifically for
> >that OS; fixing those would be helpful, since there aren't too many
> >Windows hackers here.
>
> Windows! Yeah, that'd be an amazing help. I went to go build parrot
> on Oni over the weekend to see how it went. Failed under both cygwin
> and VS/.NET, both because of ICU. (Cygwin was linking against a
> nonexistent ICU library, and the VS/.NET makefile was looking for an
> msdev executable to do something or other, but VS/.NET doesn't *have*
> an msdev program shipped with it...)
> --
> Dan
>
> --------------------------------------it's like this-------------------
> Dan Sugalski even samurai
> d...@sidhe.org have teddy bears and even
> teddy bears get drunk
>
--
"Computer Science is merely the post-Turing Decline of Formal Systems Theory."
-???
Brent 'Dax' Royal-Gordon
> I didn't/don't have VS.NET, so my implementation in icu.pl only works for
> VS6. Sorry. The basic problem is that we have to build from the VS6
> project files at the moment. There is, I believe, a way to convert these to
> makefiles which we'd ship with Parrot and then simply reference from the
> main makefile.
Matt Diephouse
<prat...@yahoo.com> wrote:
> I was wondering, whether I would just remain a mere
> spectator, or will I get an opportunity to do anything
> as well.
Please! Jump in!
> Since I am a new comer to your group, I would
> appreciate if someone could give me some directions. I
> don't want to waste your time, as I know you guys are
> extremely busy, but I would like to help, if I could
> in anyways !
There are several ways to get involved. You'll have to pick which one
best suits you based on your experience, skills, and motivation. Here
are a couple areas where you could start:
o Write tests!
o Write documentation
o Tackle something on the TODO List: http://www.parrotcode.org/todo.html
o Squash a bug from RT: http://rt.perl.org/
o Work on Ponie: http://www.nntp.perl.org/group/perl.ponie.dev/347
o Implement a new language in PASM/PIR
The important part is just to pick something and do it.
--
matt
Ron Blaschke
>> Windows! Yeah, that'd be an amazing help. I went to go build parrot
>> on Oni over the weekend to see how it went. Failed under both cygwin
>> and VS/.NET, both because of ICU. (Cygwin was linking against a
>> nonexistent ICU library, and the VS/.NET makefile was looking for an
>> msdev executable to do something or other, but VS/.NET doesn't *have*
>> an msdev program shipped with it...)
>>
> I didn't/don't have VS.NET, so my implementation in icu.pl only works for
> VS6. Sorry. The basic problem is that we have to build from the VS6
> project files at the moment. There is, I believe, a way to convert these to
> makefiles which we'd ship with Parrot and then simply reference from the
> main makefile. Doing that would help both with VS.NET and other Win32
> compilers, where VS6 is not available. Of course, it means that we're
> moving away from what's in the standard ICU distribution, but I've had to
> hack some stuff up in there anyway, IIRC.
I'm trying to help out on Windows (specifically version 13 of the compiler,
which is shipped with VS.NET or Visual C++ Toolkit 2003). Currently, I am
of little use for development, as I am looking through the source and
reading the PDDs.
I'd like to start with some patches for successful 'nmake test' anytime
soon.
But back to the main topic: I'm using the precompiled version, namely
ftp://www-126.ibm.com/pub/icu/3.0/icu-3.0-Win32-msvc7.1.zip
Unzip it, say into C:\usr\local, and put C:\usr\local\icu\bin into PATH.
Then I configure parrot w/
perl Configure.pl --icushared="C:\usr\local\icu\lib\icudata.lib
C:\usr\local\icu\lib\icuuc.lib" --icuheaders="
C:\usr\local\icu\include"
This works quite well, and I have explained it in README.win32.
By this, only 9 test failure remain, which are AFAICT, not related to ICU.
If someone gives the word, I'd be willing to look into the details of
getting the ICU version in CVS to compile as well. (I've started with that
some time ago, but stopped for some reason and switched to the precompiled
version...)
Ron
Dan Sugalski
>"Dan Sugalski" <d...@sidhe.org> wrote:
>> At 10:47 AM -0700 10/12/04, Brent 'Dax' Royal-Gordon wrote:
>> >Pratik Chandra Roy <prat...@yahoo.com> wrote:
>> >> I was wondering, whether I would just remain a mere
>> >> spectator, or will I get an opportunity to do anything
>> > > as well.
>> >
>> >If you're using Windows, there are several todo items specifically for
>> >that OS; fixing those would be helpful, since there aren't too many
>> >Windows hackers here.
>>
>> Windows! Yeah, that'd be an amazing help. I went to go build parrot
>> on Oni over the weekend to see how it went. Failed under both cygwin
>> and VS/.NET, both because of ICU. (Cygwin was linking against a
>> nonexistent ICU library, and the VS/.NET makefile was looking for an
>> msdev executable to do something or other, but VS/.NET doesn't *have*
>> an msdev program shipped with it...)
>>
Not a problem -- it generally works, which is a Good Thing. I just
don't do development on Windows, so I've no idea what this 'msdev'
thing actually does. :)
> The basic problem is that we have to build from the VS6
>project files at the moment. There is, I believe, a way to convert these to
>makefiles which we'd ship with Parrot and then simply reference from the
>main makefile. Doing that would help both with VS.NET and other Win32
>compilers, where VS6 is not available. Of course, it means that we're
>moving away from what's in the standard ICU distribution, but I've had to
>hack some stuff up in there anyway, IIRC.
I am *so* looking forward to being able to make ICU optional...