@Beaker: I don't know really. This is something I considered a few times, but I don't think the gain would justify the effort. Especially considering that it would certainly bring some confusion if the scripting language came in many different flavours. I don't reject the idea yet, but that's definitely not my priority.
@FlameDuck: are you saying what I think you're saying : being able to use BriskVM with python as the host language? (or were you speaking about python bindings for BlitzMax by any chance)
If so I must say you manage to surprise me. I wouldn't have thought I would ever get this request. This is, however, very well doable.
As for answer 4, this means you plan to use BriskVM 2 with Blitz3D/BlitzPlus ?
In any case, I now think I'm going to keep the support for host languages lacking function pointers. Lately there were some features that I was considering to add that are hard (and in some eras, impossible) to implement without funciton pointers in the host languages, hence the question. However I looked toroughly and they wouldn't fit well in BriskVM so I've dropped the idea. In addition, I already took the trouble to work around the lack of function pointers - very painfull when you need to call host functions inside of a recursive algorithm -, and this may actually be a big plus if there are other important potential host languages that have no (or lacking) function pointer support (as is the case for Blitz3D/BlitzPlus).
@FlameDuck: are you saying what I think you're saying : being able to use BriskVM with python as the host language? (or were you speaking about python bindings for BlitzMax by any chance)
If so I must say you manage to surprise me. I wouldn't have thought I would ever get this request. This is, however, very well doable.
As for answer 4, this means you plan to use BriskVM 2 with Blitz3D/BlitzPlus ?
In any case, I now think I'm going to keep the support for host languages lacking function pointers. Lately there were some features that I was considering to add that are hard (and in some eras, impossible) to implement without funciton pointers in the host languages, hence the question. However I looked toroughly and they wouldn't fit well in BriskVM so I've dropped the idea. In addition, I already took the trouble to work around the lack of function pointers - very painfull when you need to call host functions inside of a recursive algorithm -, and this may actually be a big plus if there are other important potential host languages that have no (or lacking) function pointer support (as is the case for Blitz3D/BlitzPlus).