Path: utzoo!attcan!uunet!lll-winken!lll-ncis!ati.tis.llnl.gov!paik
From: paik@ati.tis.llnl.gov (Yunki Paik)
Newsgroups: comp.databases
Subject: Re: unify 3.2 and 4.0 selsort() problems
Message-ID: <43@ncis.llnl.gov>
Date: 16 Jan 89 14:27:12 GMT
References: <1074@wpg.UUCP> <24897@sgi.SGI.COM> <1081@wpg.UUCP>
Sender: news@ncis.llnl.gov
Reply-To: paik@ati.tis.llnl.gov (Yunki Paik)
Organization: Lawrence Livermore National Laboratory, Livermore CA
Lines: 18

In article <1081@wpg.UUCP> russ@wpg.UUCP (Russell Lawrence) writes:
>
>I wouldn't be too sure of this.  Since unify traps signals, I'm not getting
>a core file, but the stubs that I've buried in my program indicate that
>my culprit is definitely the selsort function and/or its arguments.
>
>If someone out there could send me a fragment of code that works, I'd
>really appreciate the good example. 
>

For many years I have used Unify's HLI, including selsort(), without problem.
Selsort is one of the harder to understand calls, and requires careful reading
of the manual and experimentation.
Hope you give another try.

As for example code, my clients would not like it.

/yunki