Anonymous | Login | 01-17-2021 04:20 UTC |
Main | My View | View Issues | Change Log | Docs |
Viewing Issue Simple Details [ Jump to Notes ] | [ View Advanced ] [ Issue History ] [ Print ] | |||||||||||
ID | Category | Severity | Reproducibility | Date Submitted | Last Update | |||||||
0001612 | [Squeak] Kernel | minor | always | 08-05-05 00:02 | 10-28-05 21:04 | |||||||
Reporter | tim | View Status | public | |||||||||
Assigned To | ducasse | |||||||||||
Priority | normal | Resolution | open | |||||||||
Status | feedback | Product Version | ||||||||||
Summary | 0001612: [ENH] FileOutUIRemove | |||||||||||
Description |
Here is a changeset that offers a possible way around this. I know Stephane et al. are working in this area anyway so I hope it might prove useful to them in some way. "Change Set: FileOutUIRemove Date: 5 April 2003 Author: tim@sumeru.stanford.edu When we file out a class a nofitier asks if we want to include the pool dictionaries and then further notifiers ask for each pool. This is ok when there is a UI but a potential catastrophe in a shrunk system with no Display. Perhaps worse, it is simply poor engineering. This changeset illustrates an approach to avoiding this problem with the use of an Exception that has a defaultAction of simply returning true. UI tools (such as the Browser) can handle the exception an use a notifier instead. The new Exception class has a deliberately dumb name because I couldn't think of a good one. I suggest that a matching default-to-false class would be useful and a better mechanism to pass information up to the handler (or another approach entirely) would be nice. There are interesting problems in using Exceptions in this way. Writers of code have to know that an exception may be raised and how to handle it. This can mean reading a whole bunch of code in order to find out how and when the raising occurs." |
|||||||||||
Additional Information | ||||||||||||
Attached Files |
![]() |
|||||||||||
|
Mantis 1.0.8[^]
Copyright © 2000 - 2007 Mantis Group
54 total queries executed. 39 unique queries executed. |