typedef/old-style argument conflict question

[Richard O'Keefe]

I have a program where, because of its development over the years,
the following pattern occurred:

    /* in an included header file */
    typedef char *str;

    /* elsewhere */
    void make_table(len, str)
        int len;
        char *str;

I first discovered this when GCC complained about a syntax error near "str".
I don't want to defend the practice of using typedef names as arguments; it
really wasn't intentional.  My question is simply whether this code is
legal in the current ANSI draft.