> PowerPC JIT engine for Lua exists and may be integrated in MorphOS port.

I just had a look and it's nice to see that they've extended the PPC JIT engine from inconvenient e500v2 PPC to also cover standard PPC (tested on e300c4) as used by MorphOS. If that can be integrated into MorphOS Lua port I wouldn't mind seeing PPC JIT engine integrated into MorphOS Python port :-)

@Krashan,

Yes, if I were going to learn a different scripting language, it would be Lua, not Ruby, as I am not learning to try to find employment, I am only learning to better contribute to my favorite hobby.

I already have purchased all of the Hollywood products, which I understand is built on, or depends on Lua.

Getting a PowerPC JIT engine will be a very good thing for MorphOS, specially if it can be used in connection with E-UAE, for old Amiga software that cannot run without E-UAE.

Where should I look to find out more about Lua for MorphOS?

> Getting a PowerPC JIT engine will be a very good thing for MorphOS,
> specially if it can be used in connection with E-UAE

A JIT compiler that translates Lua code into PPC machine code would be of no use for translating m68k machine code into PPC machine code.
As for E-UAE, a PPC JIT compiler for that is already in the works:

https://morph.zone/modules/newbb_plus/viewtopic.php?topic_id=7476&forum=9&start=24

> Where should I look to find out more about Lua for MorphOS?

https://morph.zone/modules/news/article.php?storyid=1851
https://morph.zone/modules/news/article.php?storyid=1870

Quote:

Dave, speaking of AMOS Pro, it's my understanding, though I only ever used AMOS BASIC, that it supports graphics cards. This feature means the resulting programs are more likely to run on MorphOS. I've often thought that there must be "safe" commands that one may use in AMOS to achieve a program that compiles to a program that runs in MorphOS. The thing is, one doesn't know which commands are safe.

I wouldn't dream of asking you, except in the case where you've said you're going to muck around with AMOS anyway, but perhaps you could identify the "safe" commands and make a list and share that. Any other tips that might come to you, those too. All of this at your own convenience and timing, or not at all.

BASICs: AMOS BASIC (it's up to 1.3) was released to the public domain like eight years ago. Perhaps AMOS Pro (2.0 and later) has been by now as well. I tried AmiBlitz on MorphOS quite some time ago, and while it didn't crash right away, neither was it much functional. MorphOS could use a good BASIC. Don't know if there are other possibilities.

> AMOS BASIC (it's up to 1.3) was released to the public domain like eight years ago.

More like 11 years ago.

> Perhaps AMOS Pro (2.0 and later) has been by now as well.

According to this message on the AMOS mailing list it has been a legal free download for many years.

@Velcro_SP,

As Andreas noted, I think AMOS Pro 2.0 and beyond is now free to download and use.

I don't think it is a good choice to try to use on MorphOS and even the guys (like Samurai_Crow) who were working on trying to re-write an AMOS like replacement (it was called Matthais, or something like that), have given up on it.

I agree that it would be great to have a really good Basic for MorphOS (and there might be one that I don't know about), but from what I have read and been advised, I think AmigaE and PortablE are the best choices for me to learn with thoughts of programming for MorphOS. That plus Hollywood should be good for most programming projects that I am likely to be qualified to work on for a couple of years, until I am a better programmer.

The only reason I would mess around with AMOS Pro is because I have two complete copies of it with all the manuals, plus a lot of add-on floppy disks and CD's. There was so much PD software written with it and there are tons of source code around to look at, plus the main reason of all is that I just gave my Grandson an A500 that can run AMOS Pro and I would learn it with him, if he takes an interest in programming.

AMOS Pro would just be a help for me to learn some programming principles and do some fun stuff faster, but AmigaE and PortablE are what I see as more productive for anything I want to produce software for MorphOS, or any other Amiga flavors, since PortablE is supported for several different platforms and it is still actively being worked on my ChrisH.

One thing I have learned about myself is that I am extremely slow at getting started with any kind of programming lessons, so it is going to take a lot of time before I produce anything useful. Oh well, we all have to start somewhere at some time.

Way to go David.
I don't have much that will work in a Mac Mini, but if you need a 512MB memory strip I have one sitting around.

Krashan,
Quote:

That sounds interesting, when?

amigadave,
Quote:

It was called Mattathias, and the biggest problem to implementing a Classic Amiga-style BASIC on NG hardware is that modern graphics chipsets use floating-point (aka scientific notation) math practically everywhere. The Classic Amiga chipset was completely integer and boolean values and had absolutely no floating-point math. I wanted to make a GLSL-based Copper-list and sprite substitutes but it seems that there is not sufficient backward-compatibility in modern desktop graphics chipsets to support it.