Hi Bruce,
Good news: if you have a look at the bug report, the last comment is a
link to the GitHub pull request in which the bug is addressed.
The milestone of the pull request is 7.1.0 RC 1, so in the next version
of LiveCode 7.1 that will be released, the bug will be fixed :)
Regards,
S
Update: this is bug report 15602. The response from the Livecode folks is that
7.0.x is using 16-bit numbers for the recursionlimit property, so Jacque hit
the nail on the head. However, in 6.x.x they were using 32-bit numbers, so my
setting a very high recursion limit actually did have an effec
I have an app called “Forward Citation Generator" that looks for so-called
“forward citations” of a patent, i.e., patents that issue _after_ the target
patent that cite the target patent. It looks for forward citations of the
target patent, then looks for forward citations of that 1st generation
Bruce, I'm curious: what are you doing that requires so much recursion?
--
Richard Gaskin
Fourth World Systems
Software Design and Development for Desktop, Mobile, and Web
ambassa...@fourthworld.comhttp://www.FourthWorld.co
I thought the recursion limit was 40,000, not 400,000.
Craig Newman
-Original Message-
From: Bruce Pokras
To: How to use LiveCode
Sent: Tue, Jul 14, 2015 8:07 pm
Subject: Re: recursionlimit mystery!
> On Jul 14, 2015, at 2:57 PM, J. Landman Gay
wrote:
>
> On 7/13/201
> On Jul 14, 2015, at 2:57 PM, J. Landman Gay wrote:
>
> On 7/13/2015 9:23 PM, Bruce Pokras wrote:
>> The first time I opened the stack in 7.0.6 that had been developed
>> under 6.0.2 I received an error message related to the “openstack”
>> command in the stack script. It said that the value to
On 7/13/2015 9:23 PM, Bruce Pokras wrote:
The first time I opened the stack in 7.0.6 that had been developed
under 6.0.2 I received an error message related to the “openstack”
command in the stack script. It said that the value to which I had
set the recursionlimit property “is not a number.” The
> On Jul 11, 2015, at 4:58 PM, Bruce Pokras wrote:
>
>
>> On Jul 11, 2015, at 9:26 AM, Richard Gaskin
>> wrote:
>>
>> Bruce Pokras wrote:
>>
>>> Recently, the app's requests for the access token kept resulting in
>>> an error message. I tried a lot of differnt work-arounds. Nothing
>>> help
