On Jul 7, 2017, at 03:08:19, Quincey Morris
wrote:
>
> You didn’t look into Jens’s first suggestion: “This.” In other words, keep
> the recursion but use more than one thread.
Which was referring to my suggestion. ;) (Just to make it easier for the OP to
find what the suggestion was in the th
On Jul 6, 2017, at 22:34 , Graham Cox wrote:
>
> So… unless someone has any bright ideas (or has even read this, very
> unlikely), I’ll ponder some more.
You didn’t look into Jens’s first suggestion: “This.” In other words, keep the
recursion but use more than one thread.
What suggested itsel
> On 7 Jul 2017, at 2:44 am, Jens Alfke wrote:
>
>
>> On Jul 6, 2017, at 8:42 AM, Steve Mills wrote:
>>
>> Why can't you spawn your own thread to do the recursive code? Create the
>> NSThread, set its stack size, light its fuse to do the processing, and
>> delete it.
>
> This. Although I w
> On Jul 6, 2017, at 8:42 AM, Steve Mills wrote:
>
> Why can't you spawn your own thread to do the recursive code? Create the
> NSThread, set its stack size, light its fuse to do the processing, and delete
> it.
This. Although I would also consider looking at your code to see if it can be
re
On 6 Jul 2017, at 16:33, Graham Cox wrote:
>
> I appreciate your answer, and I realise there’s no API that could set the
> stack size after the thread is created.
>
> But presumably the stack size of the thread is set somewhere as a parameter
> to the thread when it’s created - certainly if I
On Jul 6, 2017, at 10:33:56, Graham Cox wrote:
>
>
> I appreciate your answer, and I realise there’s no API that could set the
> stack size after the thread is created.
>
> But presumably the stack size of the thread is set somewhere as a parameter
> to the thread when it’s created - certainl
> On 6 Jul 2017, at 11:04 pm, Alastair Houghton
> wrote:
>
> There’s no way an API could exist that did that - in general it’d have to
> copy the entire existing stack to a new location, then update a load of
> pointers that it has no obvious way to find (otherwise the moment you return,
> e
On 6 Jul 2017, at 06:57, Graham Cox wrote:
>
> I’m wondering if there’s a way to increase the stack size of the thread that
> opens my NSDocument in the background.
There’s no way an API could exist that did that - in general it’d have to copy
the entire existing stack to a new location, then
