Exporting functions back

Sébastien Bourdeauducq sebastien at milkymist.org
Fri Feb 24 15:33:36 CST 2012


Submitted PR 2030 and 2031.

On 02/07/2012 08:00 PM, Sébastien Bourdeauducq wrote:
> Hi,
>
> now that the VCS is functional again, could you make the modifications?
>
> Do you want a patch, or would you prefer to choose the header names
> yourself?
>
> Thanks,
> Sébastien
>
>
> On 12/29/2011 06:38 PM, Ralf Corsepius wrote:
>>> * bootp_strdup_realloc - used in the DHCP client. This means DHCP
>>> cannot be used at all at the moment.
>>> * rtems_shell_init_env - we use it with the telnet server to make the
>>> shell environment reentrant (we modify the login function).
>>> * rtems_shell_main_mv - there is no standard API for automatically
>>> moving files and directories recursively and/or across filesystems.
>>> Most UNIX applications use system() for this purpose instead of
>>> painfully reinventing the wheel, which is more or less the equivalent
>>> of calling rtems_shell_main_mv in RTEMS.
>>
>> Well, so far, these function did not have public prototypes.
>> I.e. using them qualifies as API violation and "dirty coding".
>>
>>> Can we get those functions exported again?
>>
>> I don't have any problems in making these public (... should RTEMS VCS
>> ever come up again ...).
>>
>>> (and even better, with
>>> RTEMS-specific header files
>> ACK, this would be the way to go ...
>>
>>> so we do not have to re define the
>>> prototypes ourselves)
>> ... and this is before mentioned API violation ;)
>>
>> Ralf
>>
>



More information about the rtems-users mailing list