From 81a449399607a98b7c87890aea4a2eff03498050 Mon Sep 17 00:00:00 2001 From: John Mark Bell Date: Sat, 7 Feb 2009 02:22:17 +0000 Subject: Oh look, I've changed my mind again. It's far better that the client creates computed style objects which we then populate. This will allow more efficient composition of styles as, in the most common case, it won't require any memory allocation. svn path=/trunk/libcss/; revision=6390 --- src/select/computed.c | 7 ++++--- 1 file changed, 4 insertions(+), 3 deletions(-) (limited to 'src/select/computed.c') diff --git a/src/select/computed.c b/src/select/computed.c index 6a6808b..a12e10f 100644 --- a/src/select/computed.c +++ b/src/select/computed.c @@ -7,7 +7,8 @@ #include -#include "select/computed.h" +#include + #include "utils/utils.h" /** @@ -109,7 +110,7 @@ css_error css_computed_style_destroy(css_computed_style *style) * * \param parent Parent style * \param child Child style - * \param result Pointer to location to receive composed style + * \param result Pointer to style to compose into * \return CSS_OK on success, appropriate error otherwise. * * Precondition: Parent is a fully composed style (thus has no properties @@ -117,7 +118,7 @@ css_error css_computed_style_destroy(css_computed_style *style) */ css_error css_computed_style_compose(const css_computed_style *parent, const css_computed_style *child, - css_computed_style **result) + css_computed_style *result) { UNUSED(parent); UNUSED(child); -- cgit v1.2.3