Bar() ) // returns .F.
This makes the code a lot cleaner.
> F.e. in Python which is a strongly type language,
> there is no casting, just conversion functions.
Python is a dynamically typed language (aka "duck typing").
Best regards,
--
Daniel Gonçalves
Base4 Sistemas L
t; it's not very complicated. Moreover IMO we should
> first concentrate on English only.
>
> Brgds,
> Viktor
>
> ___
> Harbour mailing list (attachment size limit: 40KB)
> Harbour@harbour-project.org
> http://lists.harbo
g/wiki/Language_code
>>>
>>> Or rather plain 'en'? Can you confirm, if this is
>>> the valid ID for dialect-neutral English language?
>>>
>>> [ Unless we want to even have separate 'US' and 'GB'
>>> English dialect docs
even have separate 'US' and 'GB'
> English dialect docs, which I believe we don't. ]
>
> Brgds,
> Viktor
>
> ___
> Harbour mailing list (attachment size limit: 40KB)
> Harbour@harbour-project.org
> h
ols.ietf.org/html/rfc5646
[2] http://www.i18nguy.com/unicode/language-identifiers.html
[3] http://en.wikipedia.org/wiki/Language_code
Regards!
--
Daniel Gonçalves
Base4 Sistemas Ltda.
[www.base4.com.br]
[twitter.com/spanazzi]
___
Harbour mailing list (attachme
now.
>>
>
>
> --
> Massimo Belgrano
> ___
> Harbour mailing list (attachment size limit: 40KB)
> Harbour@harbour-project.org
> http://lists.harbour-project.org/mailman/listinfo/harbour
>
>
--
Daniel Gonçalves
Bas
oo texty" to justify the migration.
>
> Exactly.
>
> Brgds,
> Viktor
>
> ___
> Harbour mailing list (attachment size limit: 40KB)
> Harbour@harbour-project.org
> http://lists.harbour-project.org/mailman/lis
ce 1999 up until
> today. Imagine how many lines of code would be
> written to date.
>
> Anyway, anyone can write any documentation BTW,
> but I thought it makes sense to flow existing
> information instead of reinventing the wheel
> again and again. Maybe freedom doesn't
