Skip to content
This repository
Browse code

Update readme a little bit

  • Loading branch information...
commit 2e168194acec539e24f1a23826640c7e2e47124d 1 parent b80aae5
Kresten Krab Thorup krestenkrab authored

Showing 2 changed files with 10 additions and 9 deletions. Show diff stats Hide diff stats

  1. +7 6 README.md
  2. +3 3 erjang_cfg.properties
13 README.md
Source Rendered
@@ -32,20 +32,21 @@ true
32 32 krab$
33 33 </pre>
34 34
35   -There are still things that doesn't work: a few BEAM instruction are missing some runtime support. There are also BIFs missing, or only partially implemented; we're quite careful to throw @erjang.NotImplemented@ in BIFs (or branches thereof) which are not complete. Many OTP modules need NIFs or linked-in drivers that are entirely missing or only partly implemented.
  35 +There are still things that doesn't work: We known that some aspects of `crypto` which are often needed have not been implemented. Many OTP modules need NIFs or linked-in drivers that are entirely missing or only partly implemented. When this happens, you should be getting warnings like described below.
36 36
37 37 ### Warnings
38 38
39 39 When you run Erjang, you're likely to get warnings like this:
40 40
41   -<pre>Nov 10, 2010 5:15:56 PM erjang.EModuleManager$FunctionInfo$1 invoke
42   -INFO: MISSING mnesia_sup:prep_stop/1</pre>
  41 +````
  42 +Nov 10, 2010 5:15:56 PM erjang.EModuleManager$FunctionInfo$1 invoke
  43 +INFO: MISSING mnesia_sup:prep_stop/1
  44 +````
43 45
44 46 Such warnings are perfectly OK so long as you don't see a crash that you think is related to that. It's a hint that perhaps there is a missing BIF somewhere around this. But it may also just be some optional callback API which has not been implemented.
45 47
46 48 Until Erjang is a little more complete, I'd like to keep these warnings in there.
47 49
48   -
49 50 ### What will it feel like to be running Erlang on the JVM?
50 51
51 52 Here is what to expect:
@@ -72,7 +73,7 @@ values are "/usr/lib/erlang" and "/usr/local/lib/erlang").
72 73 ## Running
73 74
74 75 <pre>renaissance:erjang krab$ ./ej
75   -Eshell V5.7.5 (abort with ^G)
  76 +Eshell V5.9.1 (abort with ^G)
76 77 1> 3+4.
77 78 7
78 79 2>
@@ -88,7 +89,7 @@ forcing Erjang to recompile next time it runs.
88 89
89 90 ### Prerequisites
90 91
91   -I have only been testing this with Erlang/OTP R13. ERJANG DOES NOT WORK WITH R14 since it introduced an incompatible API to the efile driver.
  92 +Erjang should run fine with any R14 or R15 release of OTP.
92 93
93 94 If you run with a different erts (Erlang runtime system), then you can
94 95 use the +e <ErtsVsn> flag, like this:
6 erjang_cfg.properties
... ... @@ -1,6 +1,6 @@
1   -erjang.otp.root = /usr/local/lib/erlang
2   -erjang.erts.version = 5.9
3   -erjang.otp.version = R15B
  1 +#erjang.otp.root = /usr/local/lib/erlang
  2 +#erjang.erts.version = 5.9
  3 +#erjang.otp.version = R15B
4 4
5 5 # erjang.debug.port=true
6 6 # erjang.debug.inet=true

0 comments on commit 2e16819

Please sign in to comment.
Something went wrong with that request. Please try again.