--=-1FdqKsoLk3dXTmZAGfAC Content-Type: text/plain; charset=ISO-8859-1 Content-Transfer-Encoding: 8bit I understand your concern with encapsulation. But in some situations it is interesting to have access to the inner infromation of Fontconfig, I mean, in a very few situations. Just like a big font manager, on top of Fontconfig, I can't see any other situation know... I think that the data structure is very concise, and dont need any modifications. Just a better way to access some hidden information, something like the FcConfigGet* calls. I'll see later if this idea is good. See if the compiler can solve the indirection inserted by 'typedef _FcConfig FcConfig' construction. With this sort of construction the compiler can't resolve the internal elements of structures, when accessed outside the lib. So a call returning directly the info that I need doesn't require a big change in the data structure. What do you think? Em Sex, 2004-01-02 às 15:26, Keith Packard escreveu: > Around 14 o'clock on Jan 2, Adriano Del Vigna de Almeida wrote: > > > Ok, I solved the problem adding the file 'fcint.h' into my project. This > > is the best solution? > > No. fcint.h is an internal header file for use only within the library; > it's not installed and shouldn't even be shipped in binary releases of the > system. If you do use this header file, I'm tempted to promise to break > the data structure in arbitrary ways at the next release :-) > > -keith > > > > _______________________________________________ > Fontconfig mailing list > Fontconfig@xxxxxxxxxxxxxx > http://fontconfig.org/mailman/listinfo/fontconfig > --=-1FdqKsoLk3dXTmZAGfAC Content-Type: text/html; charset=utf-8 Content-Transfer-Encoding: 7bit <!DOCTYPE HTML PUBLIC "-//W3C//DTD HTML 4.0 TRANSITIONAL//EN"> <HTML> <HEAD> <META HTTP-EQUIV="Content-Type" CONTENT="text/html; CHARSET=UTF-8"> <META NAME="GENERATOR" CONTENT="GtkHTML/3.0.9"> </HEAD> <BODY> I understand your concern with encapsulation. But in some situations it is interesting to have access to the inner infromation of Fontconfig, I mean, in a very few situations. Just like a big font manager, on top of Fontconfig, I can't see any other situation know...<BR> <BR> I think that the data structure is very concise, and dont need any modifications. Just a better way to access some hidden information, something like the FcConfigGet* calls. I'll see later if this idea is good. See if the compiler can solve the indirection inserted by 'typedef _FcConfig FcConfig' construction.<BR> <BR> With this sort of construction the compiler can't resolve the internal elements of structures, when accessed outside the lib. So a call returning directly the info that I need doesn't require a big change in the data structure.<BR> <BR> What do you think?<BR> <BR> Em Sex, 2004-01-02 às 15:26, Keith Packard escreveu: <BLOCKQUOTE TYPE=CITE> <PRE><FONT COLOR="#737373"><I>Around 14 o'clock on Jan 2, Adriano Del Vigna de Almeida wrote: > Ok, I solved the problem adding the file 'fcint.h' into my project. This > is the best solution? No. fcint.h is an internal header file for use only within the library; it's not installed and shouldn't even be shipped in binary releases of the system. If you do use this header file, I'm tempted to promise to break the data structure in arbitrary ways at the next release :-) -keith _______________________________________________ Fontconfig mailing list Fontconfig@xxxxxxxxxxxxxx</FONT> <A HREF="http://fontconfig.org/mailman/listinfo/fontconfig";><U>http://fontconfig.org/mailman/listinfo/fontconfig</U></A> <FONT COLOR="#737373"></I></FONT></PRE> </BLOCKQUOTE> </BODY> </HTML> --=-1FdqKsoLk3dXTmZAGfAC--
