On 23 February 2017 at 08:44, Giorgio Garabello <g.garabe...@gmail.com> wrote:
> Ok, many thanks to all > Wolfgang i suggest you to explain this LRESPR's "limit" in the next version > of the SMSQ/E manual. > The simplest solution would be to return an error from BP.INIT (or the equivalent SMSQ vector) when called from inside a procedure. It's not the LRESPR itself that causes the problem (it's perfectly valid to load and init something into RESPR/ALCHP from a procedure as long as it doesn't contain S*Basic extensions). However not all extensions recognise this error return and thus would not report this to the user. I don't expect this to cause any harm though, the only effect would probably be that the new keywords would not work. Right now the same error occurs when your new extensions have invalid names. I got caught once when I wrote a function 'MOD' which does the same as the MOD operator but with floating-point numbers, which all QDOS versions up to JS (and probably Minerva) happily accepted but SMSQ rejected... Jan _______________________________________________ QL-Users Mailing List
