<commit_before>		The Yacas debugger program

A debugging version of yacas comes with the 
distribution. The yacas debugger consists of:
*	{./yacasdebug}, a separate program
*	{libyacasdebug.a}, a static library that can be linked in

The debug version has to be built separately from the "production"
version of Yacas (all source files have to be recompiled).

	    Why introduce a debug version?

The reason for introducing a debug version is that for a debugger 
it is often necessary to introduce features that make the interpreter
slower. For the main kernel this is unacceptable, but for a debugging
version this is defendable. It is good for testing small programs,
to see where a calculation breaks. Having certain features only
in the debug version keeps the release executable can be kept lean 
and mean, while still offering advanced debug features.

	    How to build {yacasdebug}

The yacas debugging components can be built by the command
	make debug
or, alternatively, by going into the 
{src/} directory and using the file {makefile.debug} to build 
it:

	cd src/
	make -f makefile.debug

Note the object files generated are called {*-d.o} and are suited for the
normal Yacas executable. The static library {libyacasdebug.a} is built instead
of the normal {libyacas.a}.

The file {makefile.debug} was written to compile under Linux, but
should work on other platforms with little tweaks.

After the build the debug version of Yacas can be found in the {src/} directory.

To invoke the debugger, type

	./yacasdebug --rootdir ../scripts/

The Yacas debugger assumes the current directory for scripts,
so the {--rootdir} command line option is required.

	    What does {yacasdebug} offer?

The Yacas debugger is in development still, but already has
some useful features. 

When you build {yacasdebug} and run a command, it will:
*	keep track of the memory allocated and freed, and show any memory leaks
when you quit the program.
*	show which files are loaded to read function definitions and when.
*	keep a file name and line number for each object loaded from file, for
debugging purposes.
*	show you the stack trace when evaluation goes into an infinite recursion
(equivalent of always using {TraceStack}) and print file names and line numbers
for all rules.

The {libyacasdebug.a} library is used by {proteusdebugger}, a graphical
front-end for debugging which is also still in development.

Future versions will have the ability to step through code and to
watch local and global variables while executing, modifying them
on the fly.



<commit_msg>Update the documentation to reflect that now the debug version is built by running configure --enable-debug<commit_after>		The Yacas Debugger

	    Why introduce a debug version?

The reason for introducing a debug version is that for a debugger 
it is often necessary to introduce features that make the interpreter
slower. For the main kernel this is unacceptable, but for a debugging
version this is defendable. It is good for testing small programs,
to see where a calculation breaks. Having certain features only
in the debug version keeps the release executable can be kept lean 
and mean, while still offering advanced debug features.

	    How to build the debug version of Yacas ?

The debug version has to be built separately from the "production"
version of Yacas (all source files have to be recompiled).

To build the debug version of yacas, run configure with

	./configure --enable-debug

and after that

	make

as usual.

	    What does the debug version of yacas offer?

The Yacas debugger is in development still, but already has
some useful features. 

When you build the debug version of yacas, and run a command, it will:
*	keep track of the memory allocated and freed, and show any memory leaks
when you quit the program.
*	show which files are loaded to read function definitions and when.
*	keep a file name and line number for each object loaded from file, for
debugging purposes.
*	show you the stack trace when evaluation goes into an infinite recursion
(equivalent of always using {TraceStack}) and print file names and line numbers
for all rules.

Future versions will have the ability to step through code and to
watch local and global variables while executing, modifying them
on the fly.




{'fraction_non_alphanumeric': 0.03774464119291705, 'fraction_numerical': 0.0, 'mean_word_length': 4.141317365269461, 'pattern_counts': {'":': 0, '<': 3, '<?xml version=': 0, '>': 3, 'https://': 0, 'lorem ipsum': 0, 'www.': 0, 'xml': 0}, 'pii_count': 0, 'substrings_counts': 0, 'word_list_counts': {'cursed_substrings.json': 0, 'profanity_word_list.json': 0, 'sexual_word_list.json': 0, 'zh_pornsignals.json': 0}}
{'dir': 'git-commits-cleaned', 'id': '4213767', 'n_tokens_mistral': 1119, 'n_tokens_neox': 1065, 'n_words': 675}