Re: [Ql-Users] Problem loading extensions

2017-02-23 Thread Jan Bredenbeek
On 23 February 2017 at 08:44, Giorgio Garabello 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

Re: [Ql-Users] Problem loading extensions

2017-02-22 Thread Giorgio Garabello
Ok, many thanks to all Wolfgang i suggest you to explain this LRESPR's "limit" in the next version of the SMSQ/E manual. Giorgio 2017-02-23 6:19 GMT+01:00 Wolf : > Hi, > > Even if never fixed, any chance you could share what you found as the >> cause? >> >> > Sure thing. > > This is how I see th

Re: [Ql-Users] Problem loading extensions

2017-02-22 Thread Wolf
Hi, Even if never fixed, any chance you could share what you found as the cause? Sure thing. This is how I see the error arises: First When you call the vector to initialise new keywords, the corresponding routine (at label "sb_inipr" in smsq_sbas_inipr_asm) allocates new memory for the n

Re: [Ql-Users] Problem loading extensions

2017-02-22 Thread Martyn Hill
Sounds interesting Wolfgang! Even if never fixed, any chance you could share what you found as the cause? M. On 22/02/2017 22:30, Wolf wrote: Hi all, I've found the source of the error and this seems to be a genuine bug. However, I'm not sure that the effort required to correct this whilst

[Ql-Users] Problem loading extensions

2017-02-22 Thread Wolf
Hi all, I've found the source of the error and this seems to be a genuine bug. However, I'm not sure that the effort required to correct this whilst making sure that nothing else will be broken at the same time, will be worthwhile. So perhaps it's best to go with Martyn Hill's suggestion : do

Re: [Ql-Users] Problem loading extensions

2017-02-20 Thread Dilwyn Jones
Bob Spelten wrote: Strangely I can. When run, the system hangs (padlock) so not a total crash. I did replace the DBAS inside LAUNCH with ENV_bin from the first code block, no point in doing DBAS twice. I do remember a long time ago I had a similar problem in my BOOT and Jochen Merz advised m

Re: [Ql-Users] Problem loading extensions

2017-02-20 Thread Bob Spelten
Op Mon, 20 Feb 2017 15:22:16 +0100 schreef Marcel Kilgus : Giorgio Garabello wrote: If I try to load an extension in the usual way (LRESPR filename) and then load the other using the table QPC2 crash Code: Select all 100 WTV 105 LRESPR WIN1_DBAS_sys 110 LAUNCH 120 DEFine PROCedure LAUNCH 13

Re: [Ql-Users] Problem loading extensions

2017-02-20 Thread Marcel Kilgus
Giorgio Garabello wrote: > If I try to load an extension in the usual way (LRESPR filename) and then > load the other using the table QPC2 crash > Code: Select all > 100 WTV > 105 LRESPR WIN1_DBAS_sys > 110 LAUNCH > 120 DEFine PROCedure LAUNCH > 130DIM TAB_EXT$(2,50) > 140TAB_EXT$(0) = "WIN

Re: [Ql-Users] Problem loading extensions

2017-02-20 Thread Giorgio Garabello
Many thanks! 2017-02-20 14:40 GMT+01:00 Martyn Hill : > Ciao Giorgio > > Some time ago, I observed and reported here a similar sounding issue > whereby LRESPR would fail from within an SBasic PROCedure. Not all of them, > but some. > > I resorted to loading the very same extensions outside of a p

Re: [Ql-Users] Problem loading extensions

2017-02-20 Thread Martyn Hill
Ciao Giorgio Some time ago, I observed and reported here a similar sounding issue whereby LRESPR would fail from within an SBasic PROCedure. Not all of them, but some. I resorted to loading the very same extensions outside of a procedure, without issue. Regards, Martyn Hill. On 19/02/2017

[Ql-Users] Problem loading extensions

2017-02-19 Thread Giorgio Garabello
HI, on QPC2 I wrote a small test program, in which load the names of several extensions in a table and then load (LRESPR) scanning the table. Code: Select all 100 WTV 110 LAUNCH 120 DEFine PROCedure LAUNCH 130DIM TAB_EXT$(3,50) 140TAB_EXT$(0) = "WIN1_CLAVIER_bin" 150TAB_EXT$(1) = "WIN1