From mboxrd@z Thu Jan 1 00:00:00 1970 X-Spam-Checker-Version: SpamAssassin 3.4.4 (2020-01-24) on polar.synack.me X-Spam-Level: X-Spam-Status: No, score=-0.9 required=5.0 tests=BAYES_00,FORGED_GMAIL_RCVD, FREEMAIL_FROM autolearn=no autolearn_force=no version=3.4.4 X-Google-Thread: 103376,86f62fb0f98ad93e X-Google-NewGroupId: yes X-Google-Attributes: gida07f3367d7,domainid0,public,usenet X-Google-Language: ENGLISH,ASCII Path: g2news1.google.com!postnews.google.com!d17g2000yqb.googlegroups.com!not-for-mail From: Warren Newsgroups: comp.lang.ada Subject: Re: Passing Ada Proc as a C Function Pointer Date: Wed, 4 Aug 2010 17:45:19 -0700 (PDT) Organization: http://groups.google.com Message-ID: <581d2a1a-d7bb-48f5-9ca6-ae3c0e27c9bf@d17g2000yqb.googlegroups.com> References: NNTP-Posting-Host: 216.121.235.102 Mime-Version: 1.0 Content-Type: text/plain; charset=ISO-8859-1 Content-Transfer-Encoding: quoted-printable X-Trace: posting.google.com 1280969119 32549 127.0.0.1 (5 Aug 2010 00:45:19 GMT) X-Complaints-To: groups-abuse@google.com NNTP-Posting-Date: Thu, 5 Aug 2010 00:45:19 +0000 (UTC) Complaints-To: groups-abuse@google.com Injection-Info: d17g2000yqb.googlegroups.com; posting-host=216.121.235.102; posting-account=ENgozAkAAACH-stq5yXctoDQeZQP2E6J User-Agent: G2/1.0 X-HTTP-UserAgent: Mozilla/5.0 (Windows; U; Windows NT 5.1; en-US; rv:1.9.2.8) Gecko/20100722 Firefox/3.6.8 ( .NET CLR 3.5.30729),gzip(gfe) Xref: g2news1.google.com comp.lang.ada:12868 Date: 2010-08-04T17:45:19-07:00 List-Id: On Aug 4, 3:46=A0pm, Simon Wright wrote: > I would be a bit worried about Thread_Proc's *Ada* environment. There's > this thing called the Secondary Stack, used for - for example - string > catenation; and it's not set up here. Yikes, that could be a problem. I vaguely remember something about a "secondary stack". I'm going to need to research this. > I think you'll be OK so long as you restrain yourself! Twiddling LEDs > should be OK. Well LED twiddling is just the "hello world" test. I hope to do a lot more than that, down the road! > There may be a pragma to prevent secondary stack usage? I'm all ears! ;-) Warren