🚀 go-pugleaf

Thanks for the quote from the C standard.  For C I work from the draft
standard but a little search turned up the same thing although with a
different footnote number.  (I bought the C++ standard [multiple times!] but
haven't yet decided to spend yet more money on the C one.)  Now that I've
looked the C++ standard implies the same thing although I couldn't find it
as clearly stated as in the C one.

.  Ed

> Alan Bellingham wrote in message
> news:glbc305oe8fpeo2u3mnf0s8eajufdmtbrh@4ax.com...
>
> To quote a footnote from the current C standard:
>
>    85) A cast does not yield an lvalue.
>
> And since assignment requires an lvalue as its target, this rather
> implies that the cast-on-the-left method isn't actually legal.
>
> I suspect that it's a bug in early compilers that got left in
> because it's too useful for such code.
>
> I actually use a template:
>
>   template<typename FuncType> vool
>   WireupFunction(HINSTANCE Inst, FuncType& FnPtr, char const* FnName)
>   {
>     FnPtr = reinterpret_cast<FuncType>(GetProcAddress(Inst, FnName));
>     return (FnPtr != 0);
>   }
>
>   WireupFunction(m_Inst, ClearPrintString, "ClearPrintString");
>
> Once the template exists, it's actually less typing.