partially reversed/fixed-up b7ff56db631: avoid g_slice allocators and performance issues with memory measurements

 * Fixed build problems on Windows
 * g_slice on Windows has been shown to be of little use either
   and it does not work well with the GetProcessMemoryInfo()
   measurements.
   Also, it brings the same problem as on Glibc: Not even command-line
   termination returns the memory to the OS.
   Therefore, we don't use g_slice at all and commented on it.
 * The custom Linux and Windows memory measurement approaches
   have been shown to be inefficient.
   As a workaround, scripts disable memory limiting.
 * A better approach -- but it will only work on Glibc -- might
   be to hook into malloc(), realloc() and free() globally
   and use the malloc_usable_size() of a heap object for
   memory measurements. This will be relatively precise and cheap.
 * We still need the "Object" base class in order to measure
   memory usage as a fallback approach.

1 files changed, 2 insertions, 0 deletions

diff --git a/doc/grosciteco.tes b/doc/grosciteco.tes
index 262f2c0..e94603e 100755
--- a/doc/grosciteco.tes
+++ b/doc/grosciteco.tes
@@ -1,6 +1,8 @@
 #!/usr/local/bin/sciteco -m
 !* grosciteco.tes [-t <output-tec>] [--] <output-woman> <input> *!
 
+0,2EJ !* FIXME: Memory limiting is too slow *!
+
 :EMQ[$SCITECOPATH]/getopt.tes
 
 !* Process command-line options *!