[GRASS-dev] G__ in public API

[Huidae Cho]

I agree. One of the main reasons why G__ routines are used is there is no
alternative ways to achieve certain tasks. Then they should be exposed to
module developers. If it's not the case, those routines have to replaced
with correct G_ versions.

For example, I recently used G__mapset_permissions in g.mlist.
On Jun 10, 2014 9:33 AM, "Vaclav Petras" <wenzeslaus at gmail.com> wrote:

>
>
>
> On Tue, Jun 10, 2014 at 4:12 AM, Martin Landa <landa.martin at gmail.com>
> wrote:
>
>> Hi all,
>>
>> many of modules are using G__ functions which should be dedicated for
>> internal use only (in libs level). Those which are used by modules I
>> would suggest to rename to G_ (before GRASS 7 release).  Any
>> objections, comments?
>>
>> I agree that something must be done. It took me a while before I
> understood that double underscore methods are meant to be private (because
> of lack of documentation and bad examples in modules' code).
>
> Vaclav
>
>
> Martin
>>
>> --
>> Martin Landa * http://geo.fsv.cvut.cz/gwiki/Landa
>> _______________________________________________
>> grass-dev mailing list
>> grass-dev at lists.osgeo.org
>> http://lists.osgeo.org/mailman/listinfo/grass-dev
>>
>
>
> _______________________________________________
> grass-dev mailing list
> grass-dev at lists.osgeo.org
> http://lists.osgeo.org/mailman/listinfo/grass-dev
>
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://lists.osgeo.org/pipermail/grass-dev/attachments/20140610/24aca487/attachment.html>