#9778: Cast to array context menu item -------------------------------------+---------------------------- Reporter: bonefish | Owner: anevilyak Type: enhancement | Status: new Priority: normal | Milestone: Unscheduled Component: Applications/Debugger | Version: R1/Development Resolution: | Keywords: Blocked By: | Blocking: Has a Patch: 1 | Platform: All -------------------------------------+---------------------------- Comment (by anevilyak): Replying to [comment:10 bonefish]: > I'd keep it as is for containers like BList and BMessage where the maximum element count is fixed. In the array case it certainly doesn't harm to have the info still available, but the label should indeed be renamed. Ideally to something that indicates that this isn't fixed, maybe "Current bounds". Sounds reasonable. One last question though: Should we perhaps draw a distinction between native vs casted arrays when deciding whether or not to enforce the bounds? Since, for instance, if the source declares {{{ int x[5];}}}, then we know for a fact that the array bounds are 0-4 there, and it doesn't really make sense to allow arbitrary expansion beyond that, whereas with the case where a pointer has been casted to an array by the user, this information isn't present. > I can't reproduce the crash anymore with the new patch. Good, will commit that part later tonight then. -- Ticket URL: <http://dev.haiku-os.org/ticket/9778#comment:11> Haiku <http://dev.haiku-os.org> Haiku - the operating system.