[Scilab-Dev] hist3d() => bar3d() : schedule

[Samuel Gougeon]

Hello,

Le 04/01/2018 à 20:18, Samuel Gougeon a écrit :
>
> Hello all,
>
> I would like to implement the proposal posted @ 
> http://bugzilla.scilab.org/14738 :
>
> /hist3d() is a bar3d() and shall be renamed as this. It usurps an 
> actual missing hist3d() to be implemented/.
>
>
> Namely, to rename /hist3d()/ into /bar3d()/ before a /hist3d/() actual 
> reimplementation.
> If we agree about this evolution -- do we? --, at least two schedules 
> are possible:
>
>  1.  Schedule #1
>      1. Scilab 6.0.2 (~2019-01?) :
>           * hist3d() copied into bar3d()
>           * hist3d() tagged as obsolete, inviting to use bar3d()
>      2. Scilab 6.1.0 (~2020-01?) : former hist3d() removed
>      3. Scilab 6.2.0 (~2022-01?) : new actual hist3d() implemented
>
>  2. Schedule #2
>      1. Scilab 6.1.0 (~2020-01?) :
>          1. hist3d() copied into bar3d()
>          2. hist3d() tagged as obsolete, inviting to use bar3d()
>      2. Scilab 6.2.0 (~2022-01?) : former hist3d() removed
>      3. Scilab 6.3.0 (~2024-06?) : new actual hist3d() implemented
>
> What's your opinion about this topic?
>

Without feedback / objection by the next 2 weeks, i will propose to 
clone hist3d() => bar3d() and will warnobsolete hist3d() on the 6.0.x 
branch, for the shortest schedule.

Thanks.

Best regards
Samuel
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <https://lists.scilab.org/pipermail/dev/attachments/20180108/87eb1ce3/attachment.htm>