[Fribidi-discuss] (Justified?) compilation warning (fwd)

[Behdad Esfahbod]

On Sat, 28 Sep 2002, Shachar Shemesh wrote:

> Basically, I think you are trying to implement function overloading. I 
> wish to devide the discussion to two parts.
> 
> A. How is the right function going to be selected.
> B. How is each function going to be implemented.
> Somewhere along the discussion, another question poped in. Namely:
> C. How is the right function going to be distributed to the end user.
> 
> In the patch you sent, the answers were (as far as my understanding goes):
> A. Automatically, according to the first argument's type (assuming it's 
> the right type)

I like the idea of selection according to the first argument's 
type, but seems that I should forget it.

> B. Either no reference was made, or suggested reimplementation for each 
> size (different sources).

Same source, In what I'm thinking of, the main functions are the 
same, and the wrappers do the casts.  Some small functions may 
need three implementations though.

> C. Outside the scope of a source file.
> 
> My suggestion is along the lines of the attached code:
> A. A default is set, and user can override it by calling a specific 
> function's name (The win32 way).
> B. Common source code, optionally #ifdef.
> C. Leave this to the packagers, with an optional request (upstream 
> request) to package all encodings together.
> 
> The actual attached code will come in a little while, in a seperate mail.
> 
>                 Shachar
> 
> 
> 

-- 
Behdad Esfahbod		1 Aban 1381, 2002 Oct 23 
http://behdad.org/	[Finger for Geek Code]

#define is_persian_leap(y) ((((y)-474)%2820+2820)%2820*31%128<31)