Recent changes to considerations

WikiPage considerations modified by Raul Fajardo

Raul Fajardo — Tue, 28 Feb 2012 13:55:46 -0000

--- v3 
+++ v4 
@@ -1,4 +1,4 @@
 Considerations:
 A MUD client is basically an application using low level system services. Therefore, the small speed up and memory control achieved by a compiler and manually managing/optimizing memory is mostly irrelevant. See [Two level applications - C and your favorite runtime](http://live.gnome.org/GObjectIntrospection "GObject Introspection").
 
-MUD clients are multithtreaded applications. Thus, many MUD clients implemented in C crash due to segmentation fault. The best alternative I found was Lyntin. However, it supports many interfaces. The generality bloats the code some and some code seemed a little outdated. The whole code is perfectly commented though and looks like a great project. Check it [here](http://lyntin.sourceforge.net/ "Lyntin").
+MUD clients are multithtreaded applications. Thus, many MUD clients implemented in C crash due to segmentation fault. The best alternative I found was Lyntin. It supports many interfaces. However, the generality bloats the code and some code seemed a little outdated. The whole code is perfectly commented though and looks like a great project. Check it [here](http://lyntin.sourceforge.net/ "Lyntin").

WikiPage considerations modified by Raul Fajardo

Raul Fajardo — Tue, 28 Feb 2012 13:54:56 -0000

--- v2 
+++ v3 
@@ -1,4 +1,4 @@
 Considerations:
-A MUD client is basically an application using low level system services. Therefore, the small speed up and memory control achieved by manually a compiler and manually managing/optimizing memory is mostly irrelevant. See [Two level applications - C and your favorite runtime](http://live.gnome.org/GObjectIntrospection "GObject Introspection").
+A MUD client is basically an application using low level system services. Therefore, the small speed up and memory control achieved by a compiler and manually managing/optimizing memory is mostly irrelevant. See [Two level applications - C and your favorite runtime](http://live.gnome.org/GObjectIntrospection "GObject Introspection").
 
 MUD clients are multithtreaded applications. Thus, many MUD clients implemented in C crash due to segmentation fault. The best alternative I found was Lyntin. However, it supports many interfaces. The generality bloats the code some and some code seemed a little outdated. The whole code is perfectly commented though and looks like a great project. Check it [here](http://lyntin.sourceforge.net/ "Lyntin").

WikiPage considerations modified by Raul Fajardo

Raul Fajardo — Tue, 28 Feb 2012 13:50:27 -0000

--- v1 
+++ v2 
@@ -1,6 +1,4 @@
 Considerations:
 A MUD client is basically an application using low level system services. Therefore, the small speed up and memory control achieved by manually a compiler and manually managing/optimizing memory is mostly irrelevant. See [Two level applications - C and your favorite runtime](http://live.gnome.org/GObjectIntrospection "GObject Introspection").
 
-MUD clients are multithtreaded applications. Thus, many MUD clients implemented in C crash due to segmentation fault. 
-
-The best alternative I found was Lyntin. However, it supports many interfaces. The generality bloats the code some and some code seemed a little outdated. The whole code is perfectly commented though and looks like a great project. Check it [here](http://lyntin.sourceforge.net/ "Lyntin").
+MUD clients are multithtreaded applications. Thus, many MUD clients implemented in C crash due to segmentation fault. The best alternative I found was Lyntin. However, it supports many interfaces. The generality bloats the code some and some code seemed a little outdated. The whole code is perfectly commented though and looks like a great project. Check it [here](http://lyntin.sourceforge.net/ "Lyntin").

WikiPage considerations modified by Raul Fajardo

Raul Fajardo — Tue, 28 Feb 2012 13:49:47 -0000

Considerations: A MUD client is basically an application using low level system services. Therefore, the small speed up and memory control achieved by manually a compiler and manually managing/optimizing memory is mostly irrelevant. See [Two level applications - C and your favorite runtime](http://live.gnome.org/GObjectIntrospection "GObject Introspection"). MUD clients are multithtreaded applications. Thus, many MUD clients implemented in C crash due to segmentation fault. The best alternative I found was Lyntin. However, it supports many interfaces. The generality bloats the code some and some code seemed a little outdated. The whole code is perfectly commented though and looks like a great project. Check it [here](http://lyntin.sourceforge.net/ "Lyntin").