Hot code loading - Revision history

Skvamme: /* Example Code */

2008-12-09T21:13:37Z

‎Example Code

2008-12-07T22:57:05Z

‎To change a running Erlang system

2008-12-06T09:25:12Z

‎To change a running erlang system

2008-12-06T09:00:57Z

‎HotLoad the code

2008-12-05T22:48:40Z

2008-12-05T22:42:22Z

‎To change a running erlang system

2008-12-05T22:25:13Z

‎To change a running erlang system

2008-12-05T22:18:18Z

‎HotLoad the code

2008-12-05T22:13:33Z

‎Start an erlang node on your host

2008-12-05T22:13:20Z

‎Start an erlang node on your host

@@ Line 46: / Line 46: @@
 ==Example Code==
-There is only one thing you must know when using hot code loading, and that is what makes your code reload. Every time the erlang VM finds a module_name:function_name() in your code it looks for (and uses) the most recent version it has loaded. So - just export your loop function and preface it in your calls with the module macro ?MODULE:
+There is only one thing you must know when using hot code loading, and that is what makes your code reload. Every time the erlang VM finds a module_name:function_name() in your code it looks for (and uses) the most recent version it has loaded. So - just export your loop function and preface it in your calls with the module name or with the macro ?MODULE:
 <pre>

@@ Line 2: / Line 2: @@
 For most of us it's a cool experience to be able to inject compiled code into a running VM and instantly watch the system change.
-=== Start an erlang node on your host===
+=== Start an erlang node on your neo===
 This is my /etc/X11/Xsession.d/80zhone. As you can see the erlang node's got a name "-name neo@192.168.0.202" (a running erlang virtual machine is called an erlang node). And it's got a cookie "-setcookie SFEWRG34AFDSGAFG35235". This is all that's needed on the neo.
@@ Line 13: / Line 13: @@
 </pre>
+=== Start an erlang node on your host===
 Every erlang node in your network should have a unique name, and a common cookie. Start an erlang node on your host PC with a unique name and the common cookie:
 <pre>

← Older revision		Revision as of 09:25, 6 December 2008
Line 1:		Line 1:
−	== To change a running ~~erlang~~ system ==	+	== To change a running [[Erlang]] system ==
	For most of us it's a cool experience to be able to inject compiled code into a running VM and instantly watch the system change.		For most of us it's a cool experience to be able to inject compiled code into a running VM and instantly watch the system change.

@@ Line 32: / Line 32: @@
 === HotLoad the code ===
-To carry out Hot Code Loading type - on your host erlang console - and make sure erlang can find the compiled module 'your_modulename' on the local file system:
+Make sure erlang can find the compiled module 'your_modulename' on the local file system.
 <pre>
 net_adm:ping('neo@192.168.0.202').

← Older revision		Revision as of 22:48, 5 December 2008
Line 59:		Line 59:
	end.		end.
	</pre>		</pre>
		+
		+	[[Category:Application Developer]]

@@ Line 1: / Line 1: @@
 == To change a running erlang system ==
-For most of us it's a cool experience to be able to inject compiled code into a running VM and instantly watch the change.
+For most of us it's a cool experience to be able to inject compiled code into a running VM and instantly watch the system change.
 === Start an erlang node on your host===

← Older revision		Revision as of 22:25, 5 December 2008
Line 1:		Line 1:
	== To change a running erlang system ==		== To change a running erlang system ==
		+	For most of us it's a cool experience to be able to inject compiled code into a running VM and instantly watch the change.

	=== Start an erlang node on your host===		=== Start an erlang node on your host===

@@ Line 18: / Line 18: @@
 </pre>
-One again - first make sure you can access your neo from the host with ping, ssh ,rcp etc. Then, from your host erlang console try
+Once again - first make sure you can access your neo from the host with ping, ssh ,rcp etc. Then, from your host erlang console try
 <pre>
 net_adm:ping('neo@192.168.0.202').