On 20/08/2011, at 4:05 AM, DeNigris Sean wrote:
>> "assignments are a metalevel change from functions, and therefore should not
>> be dealt with at the same level"
> What makes them so?
> Even though I encapsulate my domain concepts, inside my objects I write (and
> see everywhere in Smalltalk) code which seems to violate what you're saying.
> Like if I was modelling a web page, maybe I'd have an instance creation
> method Webpage class>>at: aUrl; then during initialization:
> Webpage>>setUrl: aUrl
> contents := aUrl retrieveContents contents.
> ...
> So here again is assignment mixed with functions (or do you really mean
> "functions" and not messages as here?). But what is the alternative? A
> WebpageContents class? What would the benefit be?
>
Perhaps he means function (ie method) definition, as averse to function calling.
Julian.
_______________________________________________
fonc mailing list
[email protected]
http://vpri.org/mailman/listinfo/fonc
