comparison libvo/font_load_ft.c @ 17566:f580a7755ac5

Patch by Stefan Huehner / stefan % huehner ! org \ patch replaces '()' for the correct '(void)' in function declarations/prototypes which have no parameters. The '()' syntax tell thats there is a variable list of arguments, so that the compiler cannot check this. The extra CFLAG '-Wstrict-declarations' shows those cases. Comments about a similar patch applied to ffmpeg: That in C++ these mean the same, but in ANSI C the semantics are different; function() is an (obsolete) K&R C style forward declaration, it basically means that the function can have any number and any types of parameters, effectively completely preventing the compiler from doing any sort of type checking. -- Erik Slagter Defining functions with unspecified arguments is allowed but bad. With arguments unspecified the compiler can't report an error/warning if the function is called with incorrect arguments. -- M���\ns Rullg���\rd

17565:dc65faaadb04

    mp_msg(MSGT_OSD, MSGL_V, "Unicode font: %d glyphs.\n", i);

    return i;
}

static font_desc_t* init_font_desc()
{
    font_desc_t *desc;
    int i;

    desc = malloc(sizeof(font_desc_t));

	}
    }
    return desc;
}

int init_freetype()
{
    int err;
    
    /* initialize freetype */
    err = FT_Init_FreeType(&library);

    mp_msg(MSGT_OSD, MSGL_V, "init_freetype\n");
    using_freetype = 1;
    return 0;
}

int done_freetype()
{
    int err;

    if (!using_freetype)
	return 0;

17566:f580a7755ac5

    mp_msg(MSGT_OSD, MSGL_V, "Unicode font: %d glyphs.\n", i);

    return i;
}

static font_desc_t* init_font_desc(void)
{
    font_desc_t *desc;
    int i;

    desc = malloc(sizeof(font_desc_t));

	}
    }
    return desc;
}

int init_freetype(void)
{
    int err;
    
    /* initialize freetype */
    err = FT_Init_FreeType(&library);

    mp_msg(MSGT_OSD, MSGL_V, "init_freetype\n");
    using_freetype = 1;
    return 0;
}

int done_freetype(void)
{
    int err;

    if (!using_freetype)
	return 0;