Hi Folks.
[update problem snipped...]
Why was CR chosen for Squeak instead of CR LF?
[Dan Ingalls replied:] "For the same kind of reason its syntax is not the same as C.
We thought, when we started playing this game in 1972, that the separate line-feed character, used to advance the platten of a teletype machine, was an anachronism, and that modern software would be designed intelligently enough to handle the entire ascii character set (in fact of all 256 characters) without getting confused."
[Norton, Chris] OK. I don't have a problem with the reasons, but I have had some (minor) difficulties with this representation under Windoze. When I open some Squeak changes files, they come up nicely formatted and presentable, but others come up as a big blob of text. I suppose this is because my tools of choice weren't "designed intelligently" as Dan suggested.
I've tried Notepad, WordPad and MS Word 98 so far. NotePad and WordPad fail miserably, but MS Word seems to work. Do any of you Windoze Squeakers have a better tool for reading these files from the File Manager or from the Explorer (besides Squeak itself)?
Also - I recently sent a change set to a friend at Squeak central who indicated that my code had the dreaded LF characters in it (using Squeak 2.3 + fixes). If it hasn't been done already, shouldn't the file in / file out routines be "bullet proofed" to keep this from happening? (wish I had the time to surf that code right now ;-)
---==> Chris
"Norton, Chris" wrote:
Hi Folks.
[Norton, Chris] OK. I don't have a problem with the reasons, but Ihave had some (minor) difficulties with this representation under Windoze. When I open some Squeak changes files, they come up nicely formatted and presentable, but others come up as a big blob of text. I suppose this is because my tools of choice weren't "designed intelligently" as Dan suggested.
I've tried Notepad, WordPad and MS Word 98 so far. NotePad andWordPad fail miserably, but MS Word seems to work. Do any of you Windoze Squeakers have a better tool for reading these files from the File Manager or from the Explorer (besides Squeak itself)?
Try TextPad ( http://www.textpad.com/ ), or my current favorite, EditPlus ( http://editplus.com/ ). Both are shareware and both do autorecognition of end-of-line conventions and will by default save a text file in the eol format it was opened in (or convert to another if you want). They both have reasonable regexp functionality (TextPad is a bit more complete there at the moment) and other features that make source code look a lot better (EditPlus also lets you easily create custom syntax colorization macros - very simple, but kinda neat).
-- Dwight
----- Original Message ----- From: Norton, Chris chrisn@Kronos.com To: squeak@cs.uiuc.edu Sent: Monday, May 03, 1999 3:40 PM Subject: [? Windows] CR instead of CR/LF (was: RE: update 1164)
[Norton, Chris] OK. I don't have a problem with the reasons, but I have had some (minor) difficulties with this representation under Windoze. When I open some Squeak changes files, they come up nicely formatted and presentable, but others come up as a big blob of text. I suppose this is because my tools of choice weren't "designed intelligently" as Dan suggested.
I've tried Notepad, WordPad and MS Word 98 so far. NotePad and WordPad fail miserably, but MS Word seems to work. Do any of you Windoze Squeakers have a better tool for reading these files from the File Manager or from the Explorer (besides Squeak itself)?
Chris, I have the same problem, and am still wondering what to do about it. I use WordPad as my default viewer, which does, I think, nearly all of the format conversion Word does. If the text is a big blob with little squares strewn throughout, I save it as an RTF file, close the viewer, and open that RTF file. That so far has fixed all of my blobs. Then I resave it as a plain text (.txt) file.
But there has to be a better way...
Shaping
But there has to be a better way...
The coolest way would be to open your file in Squeak. If for some reason it is not desirable, you can use a free Viewer for Word 97 available at http://officeupdate.microsoft.com/downloadDetails/wd97vwr32.htm. Btw, I usually either drag-and-drop files onto Viewer, or create the Viewer's shortcut in my SendTo folder and use right-click everafter.
Aibek.
On Mon, 3 May 1999, Norton, Chris wrote:
[... snip ...]
Also - I recently sent a change set to a friend at Squeak central who indicated that my code had the dreaded LF characters in it (using Squeak 2.3 + fixes). If it hasn't been done already, shouldn't the file in / file out routines be "bullet proofed" to keep this from happening? (wish I had the time to surf that code right now ;-)
This happens if you (like many of us non-Mac-Squeakers) hacked FileStream class>>#concreteStream to answer CrLfFileStream. If you do this, every file created from Squeak will have the "correct" platform-dependend line ending. The problem is CrLfFileStream's LineEndDefault that is "guessed" at image startup.
We could do several things about this: a) Make CrLfFileStream always default to Cr. b) Change file-out routines to default to Cr. c) Discard CrLfFileStream altogether.
I did a) in my image. I think b) makes sense, too. I wouldn't like c) because CrLfFileStream makes life a little bit easier and that's a Good Thing - thanks, Andreas ;-)
/bert
squeak-dev@lists.squeakfoundation.org
-
Aibek Musaev -
Bert Freudenberg -
Dwight Hughes -
Norton, Chris -
shaping＠bigfoot.com