"Error description: set: license limit exceeded"

Dar Scott dsc at swcp.com
Wed Jun 15 16:50:46 EDT 2016


I'm guessing *almost" all the scriptlimits code was removed.  Something generated the error for Dr. Hawkins.  

Maybe that part that sets the limits to zero is broken.  Maybe some file was created with the same name as the old limits file.  I'm guessing that something smashed some RAM and set the limits to nonzero.  

But, you are right, even the limits (and all limit checking) can be fully removed and the function just return a fixed string.  


> On Jun 15, 2016, at 2:32 PM, Mike Bonner <bonnmike at gmail.com> wrote:
> 
> Deprecated in this case means pointless since checking the limits shows
> that there aren't any.  Usually the connotation is "discouraged"  as in
> they'd rather you not use it but its still there for whatever reason.  (as
> dar points out, some older scripts might check it and they might break if
> it were removed)
> I guess its possible that all the scriptlimits code that keeps you from
> doing more than intended WAS cleaned up and removed, and all thats left is
> a function that always returns 0,0,0,0.
> 
> On Wed, Jun 15, 2016 at 2:19 PM, Richmond <richmondmathewson at gmail.com>
> wrote:
> 
>> That's a bit semantically slithery . . .
>> 
>> Richmond.
>> 
>> 
>> On 15.06.2016 23:16, Dar Scott wrote:
>> 
>>> The function should stick around for a little bit because some old
>>> scripts might still check.
>>> 
>>> The generation of the error is strange, though--that may indicate a need
>>> for some snipping.  I suspect there is a check that never succeeds, but
>>> never has somehow occurred.
>>> 
>>> Just for fun:
>>> https://en.wikipedia.org/wiki/Deprecation
>>> 
>>> 
>>> On Jun 15, 2016, at 2:04 PM, Mike Bonner <bonnmike at gmail.com> wrote:
>>>> 
>>>> Deprecated doesn't mean removed.  In this case, it looks like the code is
>>>> still there, but limits set to 0 (IE infinite)  Kinda surprised the code
>>>> is
>>>> still there though, doesn't seem like it would be needed for backwards
>>>> compatability. Of course excising it would (probably?) be far more than a
>>>> just a snip snip snip.
>>>> 
>>>> On Wed, Jun 15, 2016 at 1:42 PM, Richmond <richmondmathewson at gmail.com>
>>>> wrote:
>>>> 
>>>> That's interesting; putting "put the scriptLimits" into the Message Box
>>>>> of
>>>>> LC 8.0.01 Indy yields 0,0,0,0.
>>>>> 
>>>>> I *wonder why* the documentation says "deprecated"?
>>>>> 
>>>>> Richmond.
>>>>> 
>>>>> On 15.06.2016 22:20, Dar Scott wrote:
>>>>> 
>>>>> the scriptLimits()
>>>>>> 
>>>>>> I think you should still be able to put it, just drop 'the' or the
>>>>>> parentheses.
>>>>>> 
>>>>>> Why does this sound vaguely 'porno'?
>>>>> 
>>>>> 
>>>>> 
>>>>> On Jun 15, 2016, at 1:15 PM, Richmond <richmondmathewson at gmail.com>
>>>>>> 
>>>>>>> wrote:
>>>>>>> 
>>>>>>> So, (swank, swank) I opened up LC 8.0.1 Indy and typed "put the" into
>>>>>>> the
>>>>>>> Message box, then copy-pasted "scriptLimits()" across from your
>>>>>>> message,
>>>>>>> at which point the Message box contained this:
>>>>>>> 
>>>>>>> put the ÿþ
>>>>>>> 
>>>>>>> I was unable to DELETE anything in the Message Box.
>>>>>>> 
>>>>>>> which is both odd and problematic.
>>>>>>> 
>>>>>>> So, stopping trying to be clever (!) I typed "put the scriptLimits()"
>>>>>>> into the Message box and got:
>>>>>>> 
>>>>>>> Script compile error:
>>>>>>> Error description: Handler: bad command
>>>>>>> 
>>>>>>> which is also not much use.
>>>>>>> 
>>>>>>> I then opened LC 7.1.4 (because the Dictionary in Livecode 8.0.1
>>>>>>> 64-bit
>>>>>>> Linux is a non-starter)
>>>>>>> and looked up "scriptLimits()" and read:
>>>>>>> 
>>>>>>> Deprecated in Livecode 6.7.
>>>>>>> 
>>>>>>> At which point I felt bl**dy silly that I didn't check that first.
>>>>>>> 
>>>>>>> Richmond.
>>>>>>> 
>>>>>>> 
>>>>>>> On 15.06.2016 21:35, Dar Scott wrote:
>>>>>>> 
>>>>>>> I would very much like to be Indy disqualified.
>>>>>>>> 
>>>>>>>> As to the error, it seems it has come up a few times in discussions
>>>>>>>> over the years.
>>>>>>>> 
>>>>>>>> Because of the word 'set', it feels like it has to do with too many
>>>>>>>> lines in a script that is set in a standalone.  But, I thought those
>>>>>>>> limits
>>>>>>>> had been removed.  Just it case, scriptLimits() can be checked.  It
>>>>>>>> should
>>>>>>>> be 0,0,0,0.
>>>>>>>> 
>>>>>>>> Dar
>>>>>>>> 
>>>>>>>> 
>>>>>>>> 
>>>>>>>> On Jun 15, 2016, at 12:23 PM, Richmond <richmondmathewson at gmail.com>
>>>>>>>> 
>>>>>>>>> wrote:
>>>>>>>>> 
>>>>>>>>> Your income has probably just exceeded $500,000; after all, the Indy
>>>>>>>>> version of Livecode
>>>>>>>>> has a built-in income detector :P
>>>>>>>>> 
>>>>>>>>> Richmond.
>>>>>>>>> 
>>>>>>>>> On 15.06.2016 21:19, Dr. Hawkins wrote:
>>>>>>>>> 
>>>>>>>>> I am getting this error message.  This should not be happening on an
>>>>>>>>>> indy
>>>>>>>>>> license with more than a year left.
>>>>>>>>>> 
>>>>>>>>>> For that matter, I have no idea what it means:
>>>>>>>>>> 
>>>>>>>>>> Error description: set: license limit exceeded
>>>>>>>>>> 
>>>>>>>>>> _______________________________________________
>>>>>>>>>> 
>>>>>>>>> use-livecode mailing list
>>>>>>>>> use-livecode at lists.runrev.com
>>>>>>>>> Please visit this url to subscribe, unsubscribe and manage your
>>>>>>>>> subscription preferences:
>>>>>>>>> http://lists.runrev.com/mailman/listinfo/use-livecode
>>>>>>>>> 
>>>>>>>>> _______________________________________________
>>>>>>>>> 
>>>>>>>> use-livecode mailing list
>>>>>>>> use-livecode at lists.runrev.com
>>>>>>>> Please visit this url to subscribe, unsubscribe and manage your
>>>>>>>> subscription preferences:
>>>>>>>> http://lists.runrev.com/mailman/listinfo/use-livecode
>>>>>>>> 
>>>>>>>> _______________________________________________
>>>>>>> use-livecode mailing list
>>>>>>> use-livecode at lists.runrev.com
>>>>>>> Please visit this url to subscribe, unsubscribe and manage your
>>>>>>> subscription preferences:
>>>>>>> http://lists.runrev.com/mailman/listinfo/use-livecode
>>>>>>> 
>>>>>>> 
>>>>>>> 
>>>>>>> _______________________________________________
>>>>>> use-livecode mailing list
>>>>>> use-livecode at lists.runrev.com
>>>>>> Please visit this url to subscribe, unsubscribe and manage your
>>>>>> subscription preferences:
>>>>>> http://lists.runrev.com/mailman/listinfo/use-livecode
>>>>>> 
>>>>>> _______________________________________________
>>>>> use-livecode mailing list
>>>>> use-livecode at lists.runrev.com
>>>>> Please visit this url to subscribe, unsubscribe and manage your
>>>>> subscription preferences:
>>>>> http://lists.runrev.com/mailman/listinfo/use-livecode
>>>>> 
>>>>> _______________________________________________
>>>> use-livecode mailing list
>>>> use-livecode at lists.runrev.com
>>>> Please visit this url to subscribe, unsubscribe and manage your
>>>> subscription preferences:
>>>> http://lists.runrev.com/mailman/listinfo/use-livecode
>>>> 
>>>> 
>>> _______________________________________________
>>> use-livecode mailing list
>>> use-livecode at lists.runrev.com
>>> Please visit this url to subscribe, unsubscribe and manage your
>>> subscription preferences:
>>> http://lists.runrev.com/mailman/listinfo/use-livecode
>>> 
>> 
>> 
>> _______________________________________________
>> use-livecode mailing list
>> use-livecode at lists.runrev.com
>> Please visit this url to subscribe, unsubscribe and manage your
>> subscription preferences:
>> http://lists.runrev.com/mailman/listinfo/use-livecode
>> 
> _______________________________________________
> use-livecode mailing list
> use-livecode at lists.runrev.com
> Please visit this url to subscribe, unsubscribe and manage your subscription preferences:
> http://lists.runrev.com/mailman/listinfo/use-livecode
> 





More information about the use-livecode mailing list