>[snip]
>>You might call it Str2Int32, Str2Int, Dword2Num, C2Bin etc
>
>Yes, but I have the feeling that Albert's problem is that the name must be something that he can remember whenever he considers to use it. Remembrance is a function of our brain. Our brains differ. Not everybody uses the same scheme. There may be a big difference in how function names are best remembered between, what we call in Dutch, alpha's and beta's. Alpha's are those who are better in soft sciences than in exact sciences. And beta's are better in exact sciences.
>
>In fact, I think Albert has brought to our attention a quite important theme: What is the documentation quality of our naming convention?

Peter,
Let's be honest here. I can't even remember how many times and at how many places I wrote that same function and with too many different names :) (more or less with the same code - even sometimes using below library for faster execution despite harder to grasp and even buggy for someone else if s/he doesn't know the subtle differences in declare part)
I for one absolutely not good at naming for the masses. But it's not just me :) Biggest software vendors do that too. ie: CurrencyManager (would you ever think it's related with 'current' and not 'currency' -assuming all foreigners fall into thinking Currency is related with money only- well I fell:)

Declare RtlMoveMemory In WIN32API ;
	INTEGER @DestNumeric, ;
	STRING @pVoidSource, ;
	INTEGER nLength

? Str2Num("ABCD")

Function Str2Num
Lparameters tcString
Local lnValue
lnValue=0
RtlMoveMemory(@lnValue, m.tcString, Len(m.tcString))
Return m.lnValue

Cetin