From mboxrd@z Thu Jan 1 00:00:00 1970 MIME-Version: 1.0 In-Reply-To: <891DBDE5-67F0-4C8F-86C9-FF948D0EBF25@corpus-callosum.com> References: <891DBDE5-67F0-4C8F-86C9-FF948D0EBF25@corpus-callosum.com> Date: Wed, 15 May 2013 21:10:47 +0100 Message-ID: From: Charles Forsyth To: Fans of the OS Plan 9 from Bell Labs <9fans@9fans.net> Content-Type: multipart/alternative; boundary=f46d04426c5875881704dcc75869 Subject: Re: [9fans] APE: lib/ap/gen/mbwc.c Topicbox-Message-UUID: 58f353a2-ead8-11e9-9d60-3106f5b1d025 --f46d04426c5875881704dcc75869 Content-Type: text/plain; charset=UTF-8 On 15 May 2013 18:42, Jeff Sickel wrote: > Does anyone know why this one outlier mbwc.c is in libap.a? It's in ANSI's , but if mbwc.c includes that should bring in libutf in when mb* functions are called. --f46d04426c5875881704dcc75869 Content-Type: text/html; charset=UTF-8 Content-Transfer-Encoding: quoted-printable

= On 15 May 2013 18:42, Jeff Sickel <jas@corpus-callosum.com> wrote:
Does anyone know why this one outlier mbwc.c= is in libap.a?

It's in ANSI's <stdlib.h&g= t;, but if mbwc.c includes <utf.h> that should bring in libutf in whe= n mb* functions are called.
--f46d04426c5875881704dcc75869--