Path: utzoo!utgpu!news-server.csri.toronto.edu!mailrus!uunet!tut.cis.ohio-state.edu!zaphod.mps.ohio-state.edu!uwm.edu!rpi!netserv2!deven From: deven@rpi.edu (Deven T. Corzine) Newsgroups: comp.sys.amiga.tech Subject: Re: Amigix.library in progress... (was Re: Wildcards) Message-ID: Date: 23 Mar 90 20:54:27 GMT References: <102618@linus.UUCP> <5405@sugar.hackercorp.com> <5421@sugar.hackercorp.com> <5437@sugar.hackercorp.com> Organization: Rensselaer Polytechnic Institute, Troy, NY Lines: 60 In-Reply-To: peter@sugar.hackercorp.com's message of 23 Mar 90 02:59:17 GMT On 23 Mar 90 02:59:17 GMT, peter@sugar.hackercorp.com (Peter da Silva) said: Peter> Yeh, but you can't do cx#(0|1|2|3|4|5|6|7|8|9).(obj|bak|lnk|lbk) Granted. Peter> The point is that regular expressions are more powerful than Peter> wildcards. And the Amiga "wildcards" are regular expressions. True enough. Deven> No reason why some Unix shell shouldn't allow full regexps for Deven> globbing. They just don't, usually. :-) [tradition, y'know.] Peter> Well, that's the point ain't it? Yup. Deven> I would like to be able to do "Join *.c wx#(y|z) ab#c.* to '*'" Deven> and have it work as expected. Peter> Ack. Give me consistency. Give me flexibility. Deven> Why write bcopy() when there is exec.library CopyMem()? Deven> Because bcopy will handle arbitrary overlapping memory blocks, Deven> which CopyMem() does not. Peter> How about putting this in the C library level, and implement Peter> sbrk() for the lower level. malloc isn't a system call... Also, Peter> how about using ANSI C functions (memcpy, memmov, memcmp, etc) Peter> instead of the non-standard BSD ones? Because I don't want to force a static data segment. Under Unix, malloc calls sbrk() which calls brk(). Under Amigix, malloc() will call AllocMem() and sbrk() and brk() will be be either sumplistic or dummy-implemented. As for the ANSI memory functions... well, the BSD ones aren't _that_ nonstandard. But no reason not to have both ANSI and BSD ones. For example, bcopy() and memcpy() can be the same routine, just two different ways to call it. (2 stub routines & 2 #pragmas) I know the arguments are in a different order. The stub routines and pragmas can handle loading the registers in a different order without having to change the actual routine. One problem I have is that I don't have any really good reference for ANSI library functions... As for library calls vs. system calls, the division may not be the traditional ones. Deven -- Deven T. Corzine Internet: deven@rpi.edu, shadow@pawl.rpi.edu Snail: 2151 12th St. Apt. 4, Troy, NY 12180 Phone: (518) 274-0327 Bitnet: deven@rpitsmts, userfxb6@rpitsmts UUCP: uunet!rpi!deven Simple things should be simple and complex things should be possible.