From: | Alex Pilosov <alex(at)pilosoft(dot)com> |
---|---|
To: | Jan Wieck <JanWieck(at)yahoo(dot)com> |
Cc: | pgsql-hackers(at)PostgreSQL(dot)org |
Subject: | Re: functions returning records |
Date: | 2001-06-28 17:24:32 |
Message-ID: | Pine.BSO.4.10.10106281320370.598-100000@spider.pilosoft.com |
Views: | Raw Message | Whole Thread | Download mbox | Resend email |
Thread: | |
Lists: | pgsql-hackers |
On Thu, 28 Jun 2001, Jan Wieck wrote:
>
> On a third thought, you don't get anywhere with longjmp's.
> You have a call stack, do a setjmp() saving the stack
> pointer. Then you call the function, do another setjmp() here
> and do the longjmp() to #1. This restores the saved stack
> pointer, so at the very first time you do any other function
> call (lib calls included), you corrupt the stack frame at the
> current stack pointer position. If you later jump back to
> setjmp() #2 location, you'll not be able to return.
>
> You can only drop stack frames safely, you can't add them
> back, they aren't saved.
True. I withdraw the idea.
See this for a s[l]ick implementation of coroutines in C:
http://www.chiark.greenend.org.uk/~sgtatham/coroutines.html
(essentially a replacement for set of gotos)
Tis ugly, but it should work (tm).
From | Date | Subject | |
---|---|---|---|
Next Message | RISKO Gergely | 2001-06-28 19:39:18 | funny (cache (?)) bug in postgres (7.x tested) |
Previous Message | Bruce Momjian | 2001-06-28 16:53:12 | Re: Patch for multi-key GiST (current CVS) |