Xref: utzoo comp.sys.amiga.programmer:2864 comp.lang.c:38558
Path: utzoo!utgpu!news-server.csri.toronto.edu!rpi!zaphod.mps.ohio-state.edu!mips!news.cs.indiana.edu!rutgers!njin!uupsi!sugar!peter
From: peter@sugar.hackercorp.com (Peter da Silva)
Newsgroups: comp.sys.amiga.programmer,comp.lang.c
Subject: Re: Manx vs. SAS/Lattice
Message-ID: <1991Apr22.103849.3514@sugar.hackercorp.com>
Date: 22 Apr 91 10:38:49 GMT
References: <m0jQ2YL-0003PWC@reed.edu> < <stephen.672004888@cia.docs.uu.se>
Organization: Sugar Land Unix -- Houston, TX
Lines: 21

In article <stephen.672004888@cia.docs.uu.se> stephen@cia.docs.uu.se (Stephen Cooper) writes:
> {
>   SHORT xy[MAXPOINTS * 2];
>   struct Border BezierBorder =
>   {0, 0, 1, 0, COMPLEMENT, MAXPOINTS, &xy, NULL};

I think this is an illegal auto aggregate initialization. I'm surprised it
let you get away with it. I'm crossposting to comp.lang.c so the language
lawyers can have at it.

> {
>   SHORT xy[MAXPOINTS * 2];
>   struct Border BezierBorder =
>   {0, 0, 1, 0, COMPLEMENT, MAXPOINTS, NULL, NULL};

At least here the aggregate is a constant, that it can copy in. I'm still
surprised it worked. I wouldn't code like that. Try making xy and BezierBorder
static.
-- 
Peter da Silva.   `-_-'
<peter@sugar.hackercorp.com>.