# ToDo# ====## This file lists items that have to be worked on.# An entry for an item has the following tags:# * Module: the concerned class or file# * Location: a more precise location, e.g. a function# * Description: a description of the item# * Priority: the priority of the item, may be# deferrable: of no/little relevance for OBOS R1 (to be future compatible:# the next release)# low: of relevance for the next release, but not needed in the# near future# medium: of relevance for the next release, needed in the near future# high: of relevance for the next release, needed as soon as possible# urgent: of relevance for the next release, needed yesterday, i.e.# some people depend on it being finished and can't continue# with their tasks otherwise## * Requires: a list of prerequisites needed for the item to be worked on,# omitted, when empty# * Responsible: a list of people working on the item, omitted, when empty#Module: BEntryLocation: Entry.cppDescription: Definition of SYMLINK_MAX belongs to some header file. Remove it.Priority: lowModule: EntryTestLocation: InitTest1(), InitTest2()Description: Enable tests with strlen(dir + leaf) > B_PATH_NAME_LENGTH.Priority: lowRequires: - reimpl. of SetTo(const BDirectory *, const char *, bool)Module: BPathLocation: Flatten()Description: Reimplement for performance reasons. Don't call FlattenedSize().Priority: lowModule: NodeTestLocation: SyncTest()Description: Add more thorough tests.Priority: lowRequires: - OBOS kernelModule: NodeTestLocation: LockTest()Description: Implement when kernel support is available.Priority: mediumRequires: - OBOS kernelModule: BFileLocation: Read/Write[At]()Description: Verify behavior of B_OPEN_AT_END.Priority: mediumModule: FileTestLocation: PositionTest()Description: Uncomment test, when B_OPEN_AT_END behavior is understood.Priority: mediumRequires: - verification of B_OPEN_AT_END behaviorModule: BMimeType/MimeTypeTestLocation: update_mime_info(), create_app_meta_mime()Description: Find out, what is the meaning of the force parameter. It doesobviously not mean, that calling the function twice, the secondtime with force, has the same effect as calling it only at thesecond time. At least the tests indicate, that the second call,though with force, does not have any effect at all.Priority: mediumRequires:Module: VolumeTestLocation: SetNameTest()Description: Check whether the mount point is renamed properly.Priority: low