edlin | FreeDOS standard line editor | Editor library

I have modified your code and added some comments for your reference.

I'm surprised that the first bascom you found reported an error. All compilers that I've ever used for BASIC, and I believe I've used a lot of them since 1982 on, made line numbers optional and supported labels. I remember that in my first job as a professional programmer, we designed a compiler pre-processor that would insert only lines needed for proper IF, ELSE IF and END IF statements by replacing stuff with line numbers and (gasp) GOTO statements.

I still use line numbers today in my still supported VB6 accounting application thanks to MZ-Tools add-in that allows me to add and remove line numbers to my methods and function with a single button click. This allows me to use Erl (error line number) in all my error routines, also a quick one-button add to all my methods and functions, which allows me to pin-point the exact line any error occurs on.

I'm sure the compiler designers thought that line numbers were only of real use to interpreters, and perhaps the first version of bascom figured you'd develop and test with an interpreter, then compile and distribute the executable, then perhaps later versions figured developers were using text editors, especially the later versions that came with their own IDE's and who would need line numbers there? Well, we do if we want precise error reporting! That's one thing I like about Java and Eclipse. The line numbers are there so I can know exactly where the errors are, but they don't get in the way like they do in BASIC (remove line numbers, add/remove code, replace line numbers).

The lager_default_tracer module has no associated beam file because it's created at runtime. The lager application uses goldrush, which uses runtime code compilation and loading.

If you look through the goldrush sources you'll see that it calls the standard compile:forms/2 for dynamic compilation. By tracing that call, we can reconstruct the source code for lager_default_tracer using the steps below, which assume you've already cloned the lager source repository and successfully compiled it. In some of the steps, the output of the Erlang shell command is too large to put here, so those parts are abbreviated using ellipses.

1. In your already-compiled cloned lager repo directory, run rebar shell to start an Erlang shell, which ensures all necessary directories are in the Erlang load path.

2. In the shell, turn on dbg tracing and trace compile:forms/2: