doc VS simplelanguage

* list of list literals (1,2; 3,4) eqv ((1,2), (3,4));

to paraphrase Larry Walk “everyone wants the [semi] colon”

https://docs.raku.org/

amen to this … i recommend thinking about your problem in terms of effective data structures and then apply even a very simple DSL to handle access and transformations … fwiw the built in Grammars and Slang support in raku https://docs.raku.org are fantastic tools for this job.

When I was looking at the language, I didn't find the documentation "really poor". In fact I was impressed at how much of a one-stop-shop the official docs site was for both conceptual docs and API docs.

https://docs.raku.org/

The Raku Programming Language documentation already contains most (if not all) the documentation you need to deal with the issues you will confront in migrating Perl code to Raku. But, as documentation goes, the focus is on the factual differences. These blogs will try to go a little more in-depth about specific issues and provide a little more hands-on information based on my experience porting quite a lot of Perl code to Raku.

I will start working on the new version of Pod as a branch in https://github.com/raku/doc.

Well, performance has been improved by several orders of magnitude since the first release. So maybe it's time to look at https://raku.org again (or first have a look at its new documentation site https://docs.raku.org)

go to https://docs.raku.org/ and type "IO" into the search field. Behold the list that appears. Check out IO::Path or IO::Handle or whatever looks interesting. Maybe it's just me but I go "Ooh, look at all the things!".

Related: The Raku documentation does an excellent job explaining hashes/dictrionaries/associative arrays. If you've any issues, please submit a Github issue.

Raku has a lot of syntax. My first attempt at learning the language failed because I couldn't get past all the strange syntax I saw at https://docs.raku.org/. Sometimes I didn't know what the syntax was called, so I didn't know what to search for.

In the course of figuring this out, I realized that our docs also (slightly) misstate what \d means in a Regex, which led to this PR. So thanks for bringing all this up!

That sort of stuff is easy to do with Truffle (which, ironically, lets you define a language using what they call the "truffle dsl").

The SimpleLanguage tutorial language has a bigint style number scheme with efficient optimization:

https://github.com/graalvm/simplelanguage/blob/master/langua...

Truffle has no opinion on how you parse the sources. It cares about how you execute them from an intermediate Truffle guided representation produced by the parser.

In other words antlr and truffle are a great fit. We even use this pairing for our example language simplelanguage.

https://github.com/graalvm/simplelanguage

Do you have any feedback on how we could improve the docs? If so, please let us know!

I believe the easiest way to start a new Truffle language implementation is to fork SimpleLanguage [1] and turn it into your language. Did you try to do that?

[1] https://github.com/graalvm/simplelanguage

Finally, I would suggest you to take a look at the Truffle/GraalVM ecosystem(https://www.graalvm.org/graalvm-as-a-platform/language-implementation-framework/). The documentation is not exactly very elaborate, but a few good resources are Mumbler(http://cesquivias.github.io/blog/2014/10/13/writing-a-language-in-truffle-part-1-a-simple-slow-interpreter/#mumbler-language), SimpleLanguage(https://github.com/graalvm/simplelanguage), and (https://www.endoflineblog.com/graal-truffle-tutorial-part-4-parsing-and-the-trufflelanguage-class).