languages/ Cleanup
Matt Diephouse
propose that we remove the following languages from the Parrot source
tree:
- languages/conversion/
This was added more than 3.5 years ago. It's supposed to be a
BNF to Perl6 Rules translator. I don't think its ever been used, and I
couldn't figure out how to work it (I got errors when I tried using
any of the examples).
- languages/forth/
I was actually the last one to provide a patch to forth (there
were some other commits that modified things like copyright info, but
those don't count). That was 20 months ago. The implementation was
horribly dated then and things are far worse now. It needs to be
reimplemented in order to work. This was dan's beast; I'm sure he
won't care if it's removed.
- languages/miniperl/
This hasn't seen any development in 4 years. The author is no
longer involved with Parrot. With punie and perl6, I don't see why we
need it.
- languages/ruby/
This doesn't appear to have had any work done on it in the
past 3.5 years. It's nothing more than a (partial?) Parse::RecDescent
grammar. Its author is no longer involved with Parrot. It's doubtful
that what's here would be of any use to anyone now.
If no one has any objections, I'll remove these towards the end of the
week or during the weekend.
--
matt diephouse
http://matt.diephouse.com
Allison Randal
> - languages/forth/
> I was actually the last one to provide a patch to forth (there
> were some other commits that modified things like copyright info, but
> those don't count). That was 20 months ago. The implementation was
> horribly dated then and things are far worse now. It needs to be
> reimplemented in order to work. This was dan's beast; I'm sure he
> won't care if it's removed.
I was going to suggest keeping an archive of this one outside the
repository, but it's only 2 files, so I'll just keep a copy for myself.
(I'd like to revive it at some point in PGE/TGE and the old
implementation could be useful.)
> - languages/ruby/
> This doesn't appear to have had any work done on it in the
> past 3.5 years. It's nothing more than a (partial?) Parse::RecDescent
> grammar. Its author is no longer involved with Parrot. It's doubtful
> that what's here would be of any use to anyone now.
The Ruby implementation moved out to RubyForge, so this can be deleted.
(And even the external implementation needs to be updated.)
Allison
Robert Spier
> I was going to suggest keeping an archive of this one outside the
> repository, but it's only 2 files, so I'll just keep a copy for
> myself. (I'd like to revive it at some point in PGE/TGE and the old
> implementation could be useful.)
Nothing is actually _deleted_ from SVN... it just gets harder to
find. So it'll be there later if you want it.
-R
Matt Diephouse
> If no one has any objections, I'll remove these towards the end of the
> week or during the weekend.
This is done as of r12807.
Allison Randal
>
> Nothing is actually _deleted_ from SVN... it just gets harder to
> find. So it'll be there later if you want it.
Aye, I wasn't afraid it would disappear forever. But the old "What was
that deleted path I'm looking for, and what revision should I sync back
to?" makes it just hard enough to find stuff that it's preferable to
keep a copy elsewhere.
Allison
Nicholas Clark
Would this be resolved by entries in the ChangeLog?
In Perl5 the version control history is added to a Changes file, which has
each commit message along with the perforce revision number. It makes it
very easy to search for these sorts of things. I assume that it's trivial
to automate the generation of such a file for subversion, if it's desired.
Nicholas Clark
--
I'm looking for a job: http://www.ccl4.org/~nick/CV.html
Allison Randal
>
> Would this be resolved by entries in the ChangeLog?
> In Perl5 the version control history is added to a Changes file, which has
> each commit message along with the perforce revision number. It makes it
> very easy to search for these sorts of things. I assume that it's trivial
> to automate the generation of such a file for subversion, if it's desired.
It's really not a big deal. 99.99% of the time when you 'svn delete'
something, it's because you don't need it anymore. That's true here too.
There's a good chance that if/when we get around to a PGE/TGE
implementation of Forth, the old implementation won't even be useful. :)
Allison