Skip to content


Subversion checkout URL

You can clone with HTTPS or Subversion.

Download ZIP
Browse files

Fix the simple link checker

- Be more picky in which things are treated as links
- Use " instead of ' for all URLs
  • Loading branch information...
commit 167e5bb91f374ad474625964ba33c6a89cdd0c8d 1 parent bd0214a
@matthiasl authored
2  Makefile
@@ -25,7 +25,7 @@ all: obj obj/faq.html obj/t1.html local_copy_of_definions
# Make a list of links in the document. I check these manually because
# an automatic checker is likely to miss semi-dead pages.
linkcheck: $(sources)
- grep http $(sources) | cut -d \" -f 2 | sort | uniq > $(PWD)/link-check
+ egrep https?: $(sources) | cut -d \" -f 2 | sort | uniq > $(PWD)/link-check
mkdir obj
2  academic.xml
@@ -727,7 +727,7 @@ gen_tcp:send(Socket, ["GET ", Url, " HTTP/1.0", "\r\n\r\n"]).
- <p><url href=''>Erjang</url> does exactly
+ <p><url href="">Erjang</url> does exactly
that. It's an experimental system with some impressive results.
2  faq_questions.xml
@@ -20,7 +20,7 @@
<section><title>What's new?</title>
- See the <url href=''>
+ See the <url href="">
FAQ commit history on github.</url>.
2  getting_started.xml
@@ -40,7 +40,7 @@
- <p><url href=''>Learn You Some
+ <p><url href="">Learn You Some
Erlang</url> is an easy-going tutorial which takes a day or
two to get through. Alternatively, there's a <url
href=""> spartan
4 implementations.xml
@@ -222,13 +222,13 @@
Erlang/OTP distribution includes support and documentation for cross
compiling. This is described in the file at the
top of the Erlang source, available from the
- <url href=''>downloads page</url>.
+ <url href="">downloads page</url>.
Releases <em>prior</em> to R13B04 can also be cross-compiled
with a moderate amount of effort. There's a fairly
- <url href=''>
+ <url href="">
detailed writeup</url> on the trapexit wiki which covers
cross compiling between linux systems.
2  libraries.xml
@@ -170,7 +170,7 @@
There are other ways to spread your code, including
distributing it from your own website or starting a project
- at a code hosting site. <url href=''>github</url> is quite popular with Erlang developers.
+ at a code hosting site. <url href="">github</url> is quite popular with Erlang developers.
6 obtaining.xml
@@ -263,10 +263,10 @@
<marker id="repositories"/>
<p>As of R13B03 (November 2009), there is
- an <url href=''>official Git
+ an <url href="">official Git
repository</url> maintained (daily!) by the Erlang/OTP
group. There is also
- an <url href=''> unofficial
+ an <url href=""> unofficial
repository</url> which includes history before the R13B03
@@ -284,7 +284,7 @@ Where you put the actual code is up to you.
</p><p> If your code is a correction, modification or extension to an
existing part of OTP, the usual way of spreading it is via github, the
wiki has <url
If your code is a new application or library, some common ways of
4 tools.xml
@@ -168,7 +168,7 @@ BEAM and JAM files.
<em>Syntax Tools</em> do
proper source->source transforms. Among other things they
can be used to modify old code so that it no longer uses
- deprecated functions. The <url href=''>Syntax Tools Application</url> is a standard
+ deprecated functions. The <url href="">Syntax Tools Application</url> is a standard
part of Erlang.
<em>Distel/EMACS</em> supports refactoring and interactive debugging.
@@ -245,7 +245,7 @@ BEAM and JAM files.
Writing a decompiler which can turn the above example back to source
is a fifteen minute job. Writing a decompiler which handles more
complex Erlang code is more time consuming, but not much harder.
- The <url href=''>
+ The <url href="">
syntax_tools</url> application can do most of the hard work.
If the abstract code is <em>not</em> present in the
Please sign in to comment.
Something went wrong with that request. Please try again.