They should be Strings ... on Squeak and Pharo Strings and Symbols compare equal ('s' = #'s') which is a violation of the ANSI standard .... which is why they appear to work fine ... in GemStone Strings and Symbols don't compare equal and that can lead to no end of incorrect behavior ...
symbolic versions are the only place where symbols should show up in Metacello configurations....
I have hit more porting issues due to this than almost any other .... especially in tests that are written to "cut down on excess $'" when semantically the fields are "supposed to be Strings" (i.e.,the only place that Symbols ever used are the tests ... which are passing and noone is the wiser until the code is ported to a platform that conforms to the standard)...
Dale
----- Original Message -----
| From: "Sean DeNigris" <
[hidden email]>
| To: "Metacello" <
[hidden email]>
| Sent: Thursday, June 7, 2012 1:35:57 PM
| Subject: [Metacello] Strings vs. symbols
|
| Any reason to prefer one over the other? I've seen both ways and it
| doesn't seem to make a difference (other than less $' all over)...
|
| e.g. "requires: #('CreepyCrawler');" vs. "requires:
| #(CreepyCrawler);"
|