[docs, pzasm, plasmac] Update URLs

Update many http URLs to make them https

Fixes #57

CONTRIBUTING.md:
README.md:
docs/Mercury_style.txt:
docs/grades.txt:
docs/references.txt:
src/parse.m:
src/plasmac.m:
src/pzasm.m:
    As above.

CONTRIBUTING.md

@@ -7,7 +7,7 @@ contributors.
 ## Summary and legal stuff
 
 * We prefer github pull requests or patches mailed to the
-  [developers' mailing list](https://www.plasmalang.org/lists/listinfo/dev).
+  [developers' mailing list](https://plasmalang.org/lists/listinfo/dev).
   If you need to discuss a security issue confidently you can e-mail
   plasma at plasmalang dot org
 * The license of your contribution must match the project's licenses:
@@ -29,11 +29,11 @@ The project is at an early stage and therefore we are prioritising work that
 makes the language useful above things like adding compiler optimisations.
 Additionally to make bootstrapping easier (into a self-hosted language) we
 want to avoid adding code that is not necessary and will later need to be
-re-written.  The project [roadmap](http://www.plasmalang.org/roadmap.html)
+re-written.  The project [roadmap](https://plasmalang.org/roadmap.html)
 is a good place to look to know what our current and near-future focus is.
 
 Before starting it is a good idea to
-[discuss your ideas with us](https://www.plasmalang.org/lists/listinfo/dev),
+[discuss your ideas with us](https://plasmalang.org/lists/listinfo/dev),
 we may be able to give you some pointers or let you know what kinds of
 problems you may encounter.  Complex changes, especially those that require
 some design decisions should be discussed before beginning work.  For
@@ -87,8 +87,8 @@ including cherry picking and rebasing.
 Code contributions should follow the style guides as much as possible.
 Deviations that make code more readable are permitted.
 The guides are
-[Mercury style guide](http://www.plasmalang.org/docs/Mercury_style.html) and
-[C style guide](http://www.plasmalang.org/docs/C_style.html).
+[Mercury style guide](https://plasmalang.org/docs/Mercury_style.html) and
+[C style guide](https://plasmalang.org/docs/C_style.html).
 
 TODO: Provide information about project structure.
 

README.md

@@ -7,7 +7,7 @@ It is a statically typed, side-effect free single assignment language
 and will have functional programming and concurrent programming features.
 It will support deterministic parallel execution.
 For a general overview, please visit
-[http://plasmalang.org/](http://plasmalang.org/)
+[https://plasmalang.org/](https://plasmalang.org/)
 It is in early development.
 
 It is free software, distributed mostly under the MIT license, see
@@ -27,15 +27,15 @@ You will need:
 ### Mercury installation
 
 The easiest way to install Mercury is to install the
-[.deb packages](http://dl.mercurylang.org/deb/) (on Debian, Ubuntu, etc).
+[.deb packages](https://dl.mercurylang.org/deb/) (on Debian, Ubuntu, etc).
 
-Otherwise download Mercury's [source pakcage](http://dl.mercurylang.org)
+Otherwise download Mercury's [source pakcage](https://dl.mercurylang.org)
 and follow the
 installation instructions in the
 [INSTALL](https://github.com/Mercury-Language/mercury/blob/master/.INSTALL.in)
 file.
 We've made some
-[notes about grades](http://plasmalang.org/docs/grades.html)
+[notes about grades](https://plasmalang.org/docs/grades.html)
 that may help with choosing which grades you may need.
 There is also a
 [README.bootstrap](https://github.com/Mercury-Language/mercury/blob/master/README.bootstrap)

docs/Mercury_style.txt

@@ -6,9 +6,9 @@
 :toc:
 
 // For the Mercury style guide:
-// http://www.mercurylang.org/development/developers/coding_standards.html
+// https://mercurylang.org/development/developers/coding_standards.html
 // and for reference:
-// http://www.mercurylang.org/development/developer.html
+// https://mercurylang.org/development/developer.html
 
 == General Project Contributing Guide
 

docs/grades.txt

@@ -6,7 +6,7 @@ Copyright (C) 2018 Plasma Team
 License: CC BY-SA 4.0
 
 Plasma is written in Mercury
-(at least until we get to a http://www.plasmalang.org/roadmap.html[self
+(at least until we get to a https://plasmalang.org/roadmap.html[self
 hosting] stage)
 which means if you want to compile Plasma (to contribute to it) you'll need
 to build Mercury, and while there are a couple of short-cuts the long way
@@ -18,11 +18,11 @@ Each grade is made out of many grade components separated by +.+
 Shortcuts:
 
  * If you just want to run Plasma, without compiling it, then try this
-   http://plasmalang.org/plasma-static.tgz[static build].
+   https://plasmalang.org/plasma-static.tgz[static build].
    (TODO: https://github.com/PlasmaLang/plasma/issues/9[better static builds]).
  * If you want to build Plasma on x86 or x86_64 on a .deb based Linux
    system;
-   then use the http://dl.mercurylang.org/deb/[Debian packages], and edit
+   then use the https://dl.mercurylang.org/deb/[Debian packages], and edit
    Makefile to uncomment optional settings such as debugging then type
    "make".
  * If you want to build Plasma on a non-.deb system on x86 or x86_64 then
@@ -36,7 +36,7 @@ Shortcuts:
    Plasma but found this document, then read on.
 
 The Mercury project documents its grade components
-http://www.mercurylang.org/information/doc-latest/mercury_user_guide/Grades-and-grade-components.html#Grades-and-grade-components[here (retrieved 2018-03-04)],
+https://www.mercurylang.org/information/doc-latest/mercury_user_guide/Grades-and-grade-components.html#Grades-and-grade-components[here (retrieved 2018-03-04)],
 and I will be clarifying some points made there.
 This manual, when I retrieved it, mentioned a few grade components not worth
 attempting to use, these are:
@@ -162,7 +162,7 @@ Low level C::
   The threading model is N:M with IO that can block a whole "engine" of
   workers.
   The parallel conjunction operator and the 'very' experimental
-  http://paul.bone.id.au/pub/pbone-2012-thesis/[automatic parallelism]
+  https://paul.bone.id.au/pub/pbone-2012-thesis/[automatic parallelism]
   work are supported.
   This is the only combination of base grade and +par+ that support these
   features.
@@ -219,7 +219,7 @@ Profiling::
 What type of profiling to support if any.
 +prof+ and +memprof+ have a smiliar workflow.
 +profdeep+ is a
-http://mercurylang.org/documentation/papers.html#mu_01_24[very advanced profiler]
+https://mercurylang.org/documentation/papers.html#mu_01_24[very advanced profiler]
 and worth considering.
 
 These only make sense with low-level C grades.

docs/references.txt

@@ -17,8 +17,8 @@ helpful at some point.
 
 My own blog articles, the second one discusses the two above papers:
 
-* http://paul.bone.id.au/2017/12/03/compiling-closures/[Compiling closures]
-* http://paul.bone.id.au/2017/12/10/compiling-closures2/[More on closures]
+* https://paul.bone.id.au/2017/12/03/compiling-closures/[Compiling closures]
+* https://paul.bone.id.au/2017/12/10/compiling-closures2/[More on closures]
 
 === Continuations
 
@@ -126,15 +126,15 @@ A table of some http://www.pcg-random.org/[PRNGs].
 
 == Related programming languages
 
-Plasma is implemented in http://mercurylang.org[Mercury].
+Plasma is implemented in https://mercurylang.org[Mercury].
 
 Plasma is inspired by many other languages, some of them are:
 
 * http://www2.cmp.uea.ac.uk/~jrwg/Sisal/00.Contents.html[SISAL] is an
   applicative single-assignment language, like Plasma it has declarative
   semantics and an imperative-ish style.  It supported auto-parallelisation
   based on loops and streams and rivaled Fortran form performance.
-* http://mercurylang.org[Mercury] is a logic/functional language that I
+* https://mercurylang.org[Mercury] is a logic/functional language that I
   also work on.  I developed an auto-parallelisation system for Mercury and
   plan to implement one for Plasma.  After 7 years contributing to Mercury
   I'm sure other aspects of it will also influence Plasma.

src/parse.m

@@ -854,7 +854,7 @@
     %
     % The relative precedences of unary and binary operators is covered in
     % the reference manual
-    % http://www.plasmalang.org/docs/plasma_ref.html#_expressions
+    % https://plasmalang.org/docs/plasma_ref.html#_expressions
     %
 :- pred parse_expr(parse_res(ast_expression)::out,
     tokens::in, tokens::out) is det.

src/plasmac.m

@@ -235,7 +235,7 @@ catch software_error(Message) ->
 
 version(!IO) :-
     io.write_string("Plasma Compiler verison: dev\n", !IO),
-    io.write_string("http://plasmalang.org\n", !IO),
+    io.write_string("https://plasmalang.org\n", !IO),
     io.write_string("Copyright (C) 2015-2018 The Plasma Team\n", !IO),
     io.write_string("Distributed under the MIT License\n", !IO).
 

src/pzasm.m

@@ -129,7 +129,7 @@
 
 version(!IO) :-
     io.write_string("Plasma abstract machine assembler verison: dev\n", !IO),
-    io.write_string("http://plasmalang.org\n", !IO),
+    io.write_string("https://plasmalang.org\n", !IO),
     io.write_string("Copyright (C) 2015-2018 The Plasma Team\n", !IO),
     io.write_string("Distributed under the MIT License\n", !IO).