Bryce, It's every line of (eventually, if all goes well) several years worth of work. YIKES!! :) Speaking of the mac, does Wikipedia have it right? Did they change from CR to LF in OS-X? Do we plan a similar move? Regardless, I should be able to drop extra control characters either on the way out of Dolphin or into Pharo. Understood about inside strings; escaping them might work.
RE reformatting via the RB, I realize you mean well, and therefore, please do not read even a hint of hostility into this. That said, the answer is NO WAY. Far too many times, I have been saved from myself thanks to comments dated 3-6 months apart, suggesting that something had simply not settled down and required attention. If the RB ever begins to respect pre-existing formatting, I will use it more aggressively than I do now. As it is, I use it freely for up/down moves and perhpas other miscellaneous features that do not format code. I sometimes use it on new code that has not had time to accumulate meaningful comments. Once I used Dolphin's scoped refactorings (not really refactorings at all, but useful just the same) to make sweeping changes through a couple of packages, and then manually repaired the damage; it was worth it in that case. For the above reasons, I have come to disagree with Damien about using the RB to rewrite "ClassName on:" constructs. IMHO, the resulting scattering of comments would be very poor engineering practice, especially since the class-side methods can be made to answer appropriate types w/o destroying or degrading any knowledge captured in comments. There are mentions of a magic fix for this, but every time I test the RB, it continues to mishandle comments. Thanks!! Bill Wilhelm K. Schwab, Ph.D. University of Florida Department of Anesthesiology PO Box 100254 Gainesville, FL 32610-0254 Email: [EMAIL PROTECTED] Tel: (352) 273-6785 FAX: (352) 392-7029 >>> [EMAIL PROTECTED] 10/1/2008 3:50 PM >>> Bill Schwab writes: > Hello, > > I would like to tell you all the incredible things I did to get SIF > going - truth is, it loaded and just worked. The only gripe I have is > that the Pharo browsers are displaying a large number of LF or other > non-printable characters as boxes in the Pharo browsers. I have seen > Squeak do this many times, and either just ignored it or deleted them, > as my need to view the code and tolerance level allowed. It will get > old with the amount of code I plan to move. > > How would YOU fix this? Is it a SIF problem (dumping out things it > should not from Dolphin), a SIF problem (not supressing characters as > they are loaded in Pharo), or something missing in the browsers that is > expected to be fixed in Pharo? It's a line ending problem most likely. Squeak uses Mac style line endings. If there's only a few I'd delete the characters, if there's more I might try to automate it. In general automation would be a little tricky because you'd want to ignore any carriage returns in strings that you want to keep. If you know the source well enough to know that there aren't any then just write a script possibly in Squeak to remove them. It might be worthwhile trying to automatically reformat your code. That's likely to get rid of them as the RB formatter runs off the parse tree and ignores whitespace. Bryce _______________________________________________ Pharo-project mailing list [email protected] http://lists.gforge.inria.fr/cgi-bin/mailman/listinfo/pharo-project _______________________________________________ Pharo-project mailing list [email protected] http://lists.gforge.inria.fr/cgi-bin/mailman/listinfo/pharo-project
