| From: | Jan Wieck <JanWieck(at)Yahoo(dot)com> |
|---|---|
| To: | Alex Pilosov <alex(at)pilosoft(dot)com> |
| Cc: | Hannu Krosing <hannu(at)tm(dot)ee>, pgsql-hackers(at)postgresql(dot)org |
| Subject: | Re: functions returning records |
| Date: | 2001-06-28 01:08:38 |
| Message-ID: | 200106280108.f5S18cT20448@jupiter.us.greatbridge.com |
| Views: | Raw Message | Whole Thread | Download mbox | Resend email |
| Thread: | |
| Lists: | pgsql-hackers |
Alex Pilosov wrote:
> On Thu, 28 Jun 2001, Hannu Krosing wrote:
> >
> > How hard would it be to turn this around and implement RETURN AND
> > CONTINUE
> > for at least PL/PGSQL, and possibly C/Perl/Python ... ?
> Cannot talk about plpgsql, but for c this would be probably implemented
> with setjmp and with perl with goto. Probably not very complex.
Don't think so. When the function returns, the call stack
get's destroyed. Jumping back to there - er - the core dump
is not even useful any more. Or did I miss something?
Jan
--
#======================================================================#
# It's easier to get forgiveness for being wrong than for being right. #
# Let's break this rule - forgive me. #
#================================================== JanWieck(at)Yahoo(dot)com #
_________________________________________________________
Do You Yahoo!?
Get your free @yahoo.com address at http://mail.yahoo.com
| From | Date | Subject | |
|---|---|---|---|
| Next Message | Alex Pilosov | 2001-06-28 01:24:09 | Re: functions returning records |
| Previous Message | Alex Pilosov | 2001-06-28 00:10:12 | Re: functions returning records |