Path: utzoo!attcan!uunet!lll-winken!ames!sgi!scotth@harlie.SGI.COM
From: scotth@harlie.SGI.COM (Scott Henry)
Newsgroups: comp.databases
Subject: Re: unify 3.2 selsort() problems
Message-ID: <24897@sgi.SGI.COM>
Date: 13 Jan 89 16:28:47 GMT
References: <1074@wpg.UUCP>
Sender: daemon@sgi.SGI.COM
Organization: Silicon Graphics, Inc., Mountain View, CA
Lines: 38

From article <1074@wpg.UUCP>, by russ@wpg.UUCP (Russell Lawrence):
> 
> I'm working on a small unify application that will require me to use
> the unify selsort() function for the first time.
> 
> I've invoked selsort() as outlined in the unify manuals, but the
> resulting program crashes and reports "memory error".  I can't
> ascertain precisely where the problem lies because unify is
> apparently trapping signals and preventing the system from creating
> a core file.

Having just experienced the same problem... The manual entry for selsort()
is wrong. It shows the prototype as (I can't use italics):

selsort(tnum,fldtbl,srtfunc)
  int tnum, *fldtbl;
  int (*functbl[])() = {selfunc,confunc,srtfunc,tagfunc};

the argument line should read:

selsort(tnum,fldtbl,functbl)


> Has anyone else encountered selsort problems?  Any suggestions
> would be *greatly* appreciated.

I am still having problems with my application, but I _think_ they are now
not in selsort(). Good luck.

> -- 
> Russell Lawrence, WP Group, New Orleans (504) 456-0001
> {uunet,killer}!wpg!russ


## scott henry	<scotth@sgi.com>
## Silicon Graphics, Inc.
--
              Scott Henry