Ticket #315 (closed RFC: done)

Opened 5 years ago

Last modified 5 years ago

What languages to move?

Reported by: whiteknight Owned by:
Priority: normal Milestone: 1.0
Component: language Version:
Severity: medium Keywords: languages
Cc: Language:
Patch status: Platform: all

Description

We've said that we're moving all languages out of the repository except some example and utility languages. So, which ones are those? I can start moving things today if I know what things to move. Here's a list of languages that we currently have in the repo:

abc
apl
basic
befunge
bf
c99
cardinal
chitchat
cola
dotnet
eclectus
ecmascript
forth
hq9plus
jack
json
lazy-k
lisp
lolcode
lua
m4
markdown
ook
perl6 (already moved)
pheme
pipp
pir
pod
punie
pynie
regex
scheme
squaak
unlambda
urm
wmlscript
zcode

Off the top of my head I assume that pir, pod, abc, apl, and c99 (for NCI stub parsing) are likely to stay in the repo. Anything else that shouldn't be moved?

Change History

Changed 5 years ago by whiteknight

oh, and squaak is a good example that should probably stay in the repo too.

Changed 5 years ago by coke

When moving things out, please coordinate with the MAINTAINER if possible.

"You don't have to go home, but you can't stay here" - it's ok to just remove the language and then update the wiki Languages page to mark the last revision that contained the language - then the maintainer can copy it on their own.

APL is moving out. As MAINTAINER, I'll take that one.

Note that perl6 has a separate ticket and isn't entirely gone yet.

Changed 5 years ago by allison

I would keep:

abc pir c99

And move everything else to a general repository (perhaps, parrot-languages, either on parrot.org or on code.google.com)

'pod' isn't really a language, and should move to a directory for core modules (whatever we want to call it).

For that matter, 'pir' and 'c99' should probably move to 'compilers', and 'abc' to 'examples', and get rid of the languages directory entirely.

Changed 5 years ago by kjs

What about json? The version in compilers/json is currently used, but languages/json is a pct-based version. Which one is preferable? Note that compilers/json does both to and from json (parrot-json), while languages/json is just a json compiler (json->parrot).

regarding pod: I'll try to spend some cycles on it before 1.0, but no time before 0.9.1. It would be neat if it can be finished by 1.0, then there's no longer the dependency on perldoc (I know, if there's a perl dependency, it doesn't matter, but once the perl dependency's gone, the perldoc part is already solved).

Changed 5 years ago by coke

JSON - I think working both ways trumps "written in PCT". But that assumes we want JSON in core at all, which was never decided, the original version was just a proof of concept.

Regarding allison's "move" comment, I just want to reiterate that we don't have to do the 'move'. we can just do the 'remove', and let the maintainers (if any) make the new repo. (some of these don't have maintainers, and will probably die when they are removed.)

Changed 5 years ago by allison

  • status changed from new to closed
  • resolution set to done

All languages have been moved (to a custom repository, the languages repository, or examples/) or removed.

Note: See TracTickets for help on using tickets.