On 11/09/17 20:34, Gedare Bloom wrote:

The mmap() implementation has some other problems. It contains too many
conditionals. It doesn't follow the object oriented design of the file
system layer. The mmap() is basically a factory. The mmap_h handler should
construct a mapping object. A destructor is currently missing. Maybe the
mmap_h handler should use a flag to deal with construction and destruction.
Yeah. It evolved in a way that doesn't fit. The mmap_h was an
afterthought really, since my original intention was to support shared
memory objects, but file mapping was perceived useful for some
applications. Maybe open a new ticket. I don't know when I can work on
this more.

https://devel.rtems.org/ticket/3131

--
Sebastian Huber, embedded brains GmbH

Address : Dornierstr. 4, D-82178 Puchheim, Germany
Phone   : +49 89 189 47 41-16
Fax     : +49 89 189 47 41-09
E-Mail  : sebastian.hu...@embedded-brains.de
PGP     : Public key available on request.

Diese Nachricht ist keine geschäftliche Mitteilung im Sinne des EHUG.

_______________________________________________
devel mailing list
devel@rtems.org
http://lists.rtems.org/mailman/listinfo/devel

Reply via email to