Hey, I'm reading the Server Smalltalk docs and in the Using passive images section I see this note. Note: Remove all compile time constants from your code. Code cannot execute in a passive image, so the compile time constants must be modified. What does this mean by complie time constants? -Carl You received this message because you are subscribed to the Google Groups "VA Smalltalk" group. To unsubscribe from this group and stop receiving emails from it, send an email to [hidden email]. To post to this group, send email to [hidden email]. Visit this group at http://groups.google.com/group/va-smalltalk. For more options, visit https://groups.google.com/d/optout. |
Administrator
|
On Monday, July 6, 2015 at 8:34:19 AM UTC-7, Carl Gundel wrote:
--
e.g. ##(Dictionary new at: #oneKey put: #oneValue; at: #amother put: #anotherValue; ... yourself)
You received this message because you are subscribed to the Google Groups "VA Smalltalk" group. To unsubscribe from this group and stop receiving emails from it, send an email to [hidden email]. To post to this group, send email to [hidden email]. Visit this group at http://groups.google.com/group/va-smalltalk. For more options, visit https://groups.google.com/d/optout. |
Thanks Richard, So, this includes also literal arrays? #( 1 2 3 ) I assume that the expression you include is okay without the ##( ) part. -Carl On Monday, July 6, 2015 at 11:55:50 AM UTC-4, Richard Sargent wrote:
You received this message because you are subscribed to the Google Groups "VA Smalltalk" group. To unsubscribe from this group and stop receiving emails from it, send an email to [hidden email]. To post to this group, send email to [hidden email]. Visit this group at http://groups.google.com/group/va-smalltalk. For more options, visit https://groups.google.com/d/optout. |
Administrator
|
On Monday, July 6, 2015 at 9:03:31 AM UTC-7, Carl Gundel wrote:
--
I'm not sure what you are asking here. A literal expression is not a compile-time constant.
Correct. The use of ##( ... ) is what makes it a CTC, In general, avoid CTCs. There are two many limitations with them to justify their use. I really like the idea, but too much information is compiled out. (Nothing except the resulting CTC can be found in the method's literals.)
You received this message because you are subscribed to the Google Groups "VA Smalltalk" group. To unsubscribe from this group and stop receiving emails from it, send an email to [hidden email]. To post to this group, send email to [hidden email]. Visit this group at http://groups.google.com/group/va-smalltalk. For more options, visit https://groups.google.com/d/optout. |
Administrator
|
Sheesh! (I'm trying out a new keyboard, but that doesn't explain or excuse misspellings.)
-- s/two/too/ On Monday, July 6, 2015 at 9:17:10 AM UTC-7, Richard Sargent wrote:
You received this message because you are subscribed to the Google Groups "VA Smalltalk" group. To unsubscribe from this group and stop receiving emails from it, send an email to [hidden email]. To post to this group, send email to [hidden email]. Visit this group at http://groups.google.com/group/va-smalltalk. For more options, visit https://groups.google.com/d/optout. |
In reply to this post by Richard Sargent
Okay thanks. We do not have any such code in our our product, which is ported from VisualSmalltalk. -Carl On Monday, July 6, 2015 at 12:17:10 PM UTC-4, Richard Sargent wrote:
You received this message because you are subscribed to the Google Groups "VA Smalltalk" group. To unsubscribe from this group and stop receiving emails from it, send an email to [hidden email]. To post to this group, send email to [hidden email]. Visit this group at http://groups.google.com/group/va-smalltalk. For more options, visit https://groups.google.com/d/optout. |
Free forum by Nabble | Edit this page |