Re: Another bizarre phenomenon
- To: mathgroup at smc.vnet.net
- Subject: [mg51634] Re: [mg51598] Another bizarre phenomenon
- From: Christopher Purcell <christopherpurcell at mac.com>
- Date: Wed, 27 Oct 2004 23:42:34 -0400 (EDT)
- References: <200410270553.BAA24479@smc.vnet.net>
- Sender: owner-wri-mathgroup at wolfram.com
I have seen this sort of thing and invariably it was a product of using StandardForm, which is not as stable as it should be - but not too surprising since it has to deal with a lot more ambiguity. InputForm, on the other hand is rock-solid so I use it almost exclusively when writing packages. I use StandardFrom for writing "pretty" notebooks containing simple expressions, for others to read. To enforce use of InputForm you use the menu items Cell, Default Input FormatType,InputForm to override the default setting, which is likely StandardForm. To convert existing StandardForm material to InputForm I don't like using the Cell, Convert To, menu items - I find the resultant InputForm is not as readable as when I simply copy and paste into a new Cell (having previously set the Default Input Format Type to InputForm). christopherpurcell at mac.com AIM/iChatAV: cffrc On Oct 27, 2004, at 2:53 AM, Steve Gray wrote: > I replaced a 3-letter symbol with another 3-letter symbol, looking at > eachsearch and replacement. All seemed ok. Then I tried to execute the > file and it went nuts. I somehow found that if I removed JUST ONE SPACE > between the Module list of local symbols in a function definition line, > and a comment on the same line, all was OK again. Wow. This happened > at least twice, identically. Any comments? > > Steve Gray >
- References:
- Another bizarre phenomenon
- From: Steve Gray <stevebg@adelphia.net>
- Another bizarre phenomenon