Mathematica Stack Exchange is a question and answer site for users of Mathematica. Join them; it only takes a minute:

Sign up
Here's how it works:
  1. Anybody can ask a question
  2. Anybody can answer
  3. The best answers are voted up and rise to the top

I wrote a notebook on Mac OS 10.7.4 and run it on Windows XP at work. On my Mac I use a full version of Mathematia, whereas on the Windows-system only a trial version (Version

First of all I cannot run the following code on the Windows system (on Mac it works perfect):

ImportData={{"Test1", 5670.`, 0.`, 180.`, 2756.`, 2443.`, 180.`, 1008.`, 2007.`},
            {"Test2", 100.`, 0.`, 3006.`, 1235.`, 9874.`, 4543.`, 3241.`, 5004.`}}; 

WhitespaceCleaning[string_] := 
      string, (StartOfString ~~ Whitespace) | (Whitespace ~~ 
          EndOfString) :> ""]

OriginalData = 
  Drop[ImportData, 1] /. {a_, b_, cc_, d_, e_, f_, g_, h_, i_} ->
  {WhitespaceCleaning@a, {b, cc, d, e, f, g, h, i}};

However I can get the same result as on my Mac with the following code for my Windows system:


The rest of my code runs perfect (I get the same results on both operating systems). However, running my code on Windows provokes many messages (such as Divide::index, Divide::infy, Power::infy, General::stop, Less::nord, LessEqual::nord) which does not happen on my Mac.

I don't understand why Mathematica on my Windows system is acting so odd. Does anyone has an idea?

share|improve this question
The replacement is not used at all (as the left hand side of the rule does not match anything in the list), though WhitespaceCleaning@a is evaluated before any replacement is done, and its argument is not a string, so an error message is issued. Try RuleDelayed (:>) instead of simply using Rule (->). – István Zachar Jun 26 '12 at 19:48
@IstvánZachar: I replaced -> with :>. Works now on Windows. However, both -> and :> return the same result on my Mac. I don't understand why "the left hand side of the rule does not match anything in the list". In ImportData I have two lists which do match the pattern {a_, b_, cc_, d_, e_, f_, g_, h_, i_}. – John Jun 26 '12 at 19:57
Sorry, my mistake: it does match. Do you load any custom packages on your Mac? Did you make sure no previous garbage is left in the kernel? Better run on both machines with a fresh kernel. – István Zachar Jun 26 '12 at 20:03
@IstvánZachar No problem. I did not load any custom packages and I run the code with fresh kernel on both systems. Problem remains. – John Jun 26 '12 at 20:06
Note that you can use StringTrim for your whitespace cleaning: – Mike Honeychurch Jun 26 '12 at 22:22
up vote 4 down vote accepted

My feeling is that your Windows system is performing like it should and that the problem lies with your OS X system. Using the -> instead of :> causes the immediate evaluation of the right hand side of the rule yielding an expression of the form

StringReplace[a, (StartOfString ~~ Whitespace) | (Whitespace ~~ EndOfString) :> ""] 

with a still undefined. Since StringReplace expects a string as first argument it balks and generates an error message. It then returns unevaluated. Then the pattern match kicks in, a gets the value "Test2" and evaluation of StringReplace continues, now with the sting "Test2" as argument which works.

In this case the :> is the better choice.

The question should be: why doesn't your Mac version object like the Windows version does (and not the other way around)?

I see a number of options:

  • On your Mac version you have set error messages preferences (Edit > Preferences > Evaluation> Message and Warning action) to not print to the input notebook
  • You have switched off error messages using Off somewhere

You might try (on your Mac MMA) the following and see whether it generates an error message (it should):

share|improve this answer
I took MikeHoneychurch's tip into consideration and replaced WhitespaceCleaning by StringTrim and changed a_ to a_String (I didn't know that I needed to declare the type of my variables always). I changed the setting for "Message and Warning action". Still, evaluating the same code on both systems results in a red highlighted cell on Windows (hence, indicating a message) and not highlighted cell on Mac OS. However, on both systems the same messages appear (and presumably did also before). – John Jun 27 '12 at 17:42
The a_String should not be seen as a variable declaration but as a restriction of the definition to arguments of this type. Without it, WhitespaceCleaning fires on any argument including non-strings and undefined symbols which will get you errors in this case. When you add String, it is only executed when it gets an argument with head String which it can process. – Sjoerd C. de Vries Jun 27 '12 at 18:28

Your Answer


By posting your answer, you agree to the privacy policy and terms of service.

Not the answer you're looking for? Browse other questions tagged or ask your own question.