9fans - fans of the OS Plan 9 from Bell Labs
 help / color / mirror / Atom feed
From: Ryan <rymg19@gmail.com>
To: Fans of the OS Plan 9 from Bell Labs <9fans@9fans.net>,
	Ori Bernstein <ori@eigenstate.org>
Subject: Re: [9fans] New Language [Myrddin] On Plan 9/amd64
Date: Sun,  4 Jan 2015 09:13:20 -0600	[thread overview]
Message-ID: <2de32b2c-d7e4-47b0-bd2a-77300e79ef0b@email.android.com> (raw)
In-Reply-To: <20150104005900.d146d56df0f6cdab930a0fc8@eigenstate.org>

[-- Attachment #1: Type: text/plain, Size: 2981 bytes --]

That looks really neat! One question: are runtime bound checks really necessary? I would at least like a seperate release mode that gets rid of them. Writing a kernel with bound checks would be a mixed nightmare!

FYI, please tell me I'm not the only person reminded of Rust...

Ori Bernstein <ori@eigenstate.org> wrote:
>Myrddin is a language that I put together for fun, but which has
>developed
>delusions of usefulness. It's a complete reinvention of the wheel, from
>the
>ground up. Some of the major things you'll notice about it:
>
>    - Type inference. Types are inferred across the whole program.
>    - Algebraic data types.
>    - And their friend, pattern matching.
>    - Generics.
>    - A package system.
>    - Low level control over memory and such.
>    - (Almost) no runtime library.
>    - Self contained.
>
>For more details, you can look at the language website:
>
>    http://eigenstate.org/myrddin
>
>Myrddin has been ported to Plan 9/amd64, tested on 9front. I haven't
>been able
>to get 9atom's amd64 kernel to boot on virtual hardware yet, so it
>hasn't been
>tested there.
>
>The compiler and libstd should build out of the box using the provided
>mkfiles. The libs used for mbld currently need either mbld or gnu make
>in
>order to build, or you can run myrbuild by hand. I've provided a script
>that
>does the latter.
>
>Almost all Plan 9 system calls are directly supported in libsys.
>As with Linux/Unix, only amd64 targets are supported at the moment.
>
>To bootstrap the code on Plan 9, the following script is provided:
>
>	http://eigenstate.org/myrddin/getmyr.rc
>
>You can grab the script and run it as follows:
>
>	; hget http://eigenstate.org/myrddin/getmyr.rc > getmyr.rc
>	; chmod +x getmyr.rc
>	; getmyr.rc
>	...a lot of cloning and building happens...
>	; sam helloworld.myr
>
>For ease of hacking on Plan 9, I've added mercurial mirrors of the
>compiler and some libraries to bitbucket:
>
>	http://bitbucket.com/oridb/mc
>	http://bitbucket.com/oridb/libbio
>	http://bitbucket.com/oridb/libregex
>	http://bitbucket.com/oridb/libcryptohash
>	http://bitbucket.com/oridb/libdate
>	http://bitbucket.com/oridb/mbld
>
>There are a number of TODOs, of course:
>
>	- Libdate needs to learn how to parse Plan 9 timezone files.
>	- Libstd needs to get a smarter allocator for large allocations.
>	- More libraries: lib9p, libdraw, etc... all need to be written.
>	- A bit more thought needs to be given nicer, portable APIs.
>	- More Plan 9 integration.
>
>And general work to get Myrddin to the point of day to day usability,
>int terms of faster binaries, more libraries, and so on.
>
>Still, if anyone finds this interesting/useful -- have at it. If you
>manage to do something neat, let me know!
>
>-- 
>Ori Bernstein <ori@eigenstate.org>

-- 
Sent from my Android phone with K-9 Mail. Please excuse my brevity.
Check out my website: http://kirbyfan64.github.io/

[-- Attachment #2: Type: text/html, Size: 3880 bytes --]

  reply	other threads:[~2015-01-04 15:13 UTC|newest]

Thread overview: 9+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2015-01-04  8:59 Ori Bernstein
2015-01-04 15:13 ` Ryan [this message]
2015-01-04 19:45   ` Ori Bernstein
2015-01-04 19:08 ` erik quanstrom
2015-01-04 19:39   ` Ori Bernstein
2015-01-04 19:51 ` Skip Tavakkolian
2015-01-04 21:43   ` Ori Bernstein
2015-01-04 21:48 ` Winston Kodogo
2015-01-04 23:42 ` Ori Bernstein

Reply instructions:

You may reply publicly to this message via plain-text email
using any one of the following methods:

* Save the following mbox file, import it into your mail client,
  and reply-to-all from there: mbox

  Avoid top-posting and favor interleaved quoting:
  https://en.wikipedia.org/wiki/Posting_style#Interleaved_style

* Reply using the --to, --cc, and --in-reply-to
  switches of git-send-email(1):

  git send-email \
    --in-reply-to=2de32b2c-d7e4-47b0-bd2a-77300e79ef0b@email.android.com \
    --to=rymg19@gmail.com \
    --cc=9fans@9fans.net \
    --cc=ori@eigenstate.org \
    /path/to/YOUR_REPLY

  https://kernel.org/pub/software/scm/git/docs/git-send-email.html

* If your mail client supports setting the In-Reply-To header
  via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for NNTP newsgroup(s).