THIS PART IS AN ADDITION TO ORIGINAL INFORMATION FROM BACK in 1990 {or so!?}
{ReadMeFirst.txt file}, AmigaCOMAL V2.03
-----------------------------------------------------------------------------------------
-----------------------------------------------------------------------------------------


5th of September 2025

HOW DID I INSTALL IT approximately 40 YEARS LATER?
{HELL! AM I THAT OLD ALREADY??? Damn! Haha...} 
-----------------------------------------------------------------------------------------
NOTE: This is only reflecting my AmigaCOMAL experiences!
-----------------------------------------------------------------------------------------

My personal {emulated} Amiga settings:
AMIGA 500,  68030/28 , 9MB RAM {1MB CHIP, 8MB FAST}, DH0: {Workbench 1.3.3}, DH1:{Work}
AMIGA 2000, 68030/56 , 9MB RAM {1MB CHIP, 8MB FAST}, DH0: {Workbench 2.1  }, DH1:{Work}*
AMIGA 2000, 68030/JIT, 9MB RAM {1MB CHIP, 8MB FAST}, DH0: {Workbench 3.1  }, DH1:{Work}*

As can be seen, i tried all three Amiga OS Version's {excluding all newer versions!}
*mainly i used WB 1.3.3 because i just like old Workbench!
{it could be that I'll eventually change that old retro habit, or?}
-----------------------------------------------------------------------------------------

I am using Cloanto's Amiga Emulator and have just copied the content of AmigaCOMAL
Floppy-Disk {.adf} into my AmigaCOMAL folder {which is here: DH1:Coding/AmigaCOMAL}

I did NOT COPIED iff.library to libs: because i already had one, version {v18.5, WB1.3.3}

{NOTE:  I replaced the existing older version of AmigaCOMAL iff.library with this new one}
{	Therefore, check your WB 1.3.x iff.library and if it is older than v18.5, replace it}
{	with this one}

Final step, i added the following lines in 'user-startup' file {s: folder}:

	Assign Cml: dh1:Coding/AmigaCOMAL
	Assign AmigaCOMAL: dh1:Coding/AmigaCOMAL


WHY?

Because adding just Cml: as suggested, didn't worked and packages couldn't be found.
E.g. USE turtle was giving an error message because it couldn't be linked properly.
First after adding the 2nd assignment line, it was working properly and the code was
executed without any errors!


-----------------------------------------------------------------------------------------
COMPILER {Version 2.0}, {for AmigaCOMAL v2.03}
-----------------------------------------------------------------------------------------

I so badly miss that option on my COMAL-80 V2.02 for Commodore C128!

Well, here we have it in all its glory and it's working. AmigaCOMAL program which can run on any Amiga without the need to have
AmigaCOMAL installed! That's just huge and amazing.

All you need to do are few small steps {this is how i did it, but you can do it any other way you want or prefer!}:

1. write a program and save it {e.g. benchmark}, note .sav is added automatically!
2. CLOSE AmigaCOMAL {QUIT the application or DirOPUS4 might freeze!}
3. copy the file to RAM DISK: {RAM:}
4. copy following {from the AmigaCOMAL/Compiler folder to RAM:},{I use DirOpus4 to do that}
	- Blink
	- ComalComp
	- Compile
	- Compile.info
	- Runtime.obj
5. start CLI or Shell
6. type: CD RAM: {and press ENTER to change your working directory to RAM DISK}
7. type: compile benchmark -p ram: -u AmigaCOMAL:Packages {press ENTER to compile/link}

This will create a file inside your RAM DISK: with a new icon and "benchmark" name
File is now executable and can run standalone without AmigaCOMAL installed {which is great!}

What isn't so great?: It's not running any faster!
So my best guess is: the main purpose of this 'COMPILER' is to make things run as a standalone file and not necessary to also speed things up!
My second guess: I did or am doing something wrong!
Because everyone is expecting to see some acceleration when a compiler is involved, why would it here be otherwise?

I'll probably need to investigate further in the future. For now i am actually happy that it is possible and it's running!

Also a small script in C: folder would be nice to just start that, add a SourceCode name and
create a compiled standalone program! {...one day, who knows!}

