[Swift-devel] Problem with @extractint?

[Michael Wilde]

If I understood this case right, the data dependencies were logically 
correct but didnt behave so because @extractint() wasnt treated as a 
first-class value.  (Mihael, can you clarify, if I got this wrong)

I need to gather all my notes, but one point is that in the userguide 
and tutorial, early on, we should document how the data flow model 
works, how its central to swift, and some examples of how it can cause 
program behavior to be "surprising" (eg when the statements in a 
procedure execute in reverse order, or when a statement in a calling 
function executes while a called function is still active, trigerred by 
events in the callee). Until one gets this model, Swift often seems to 
violate the "principle of least astonishment" ;)

I'll save discussion on this till I get my notes out. I think the model 
is fine, and that we need to better understand how it affects 
programming and how to train users to use it (and debug in it).

On 10/9/07 9:57 AM, Mihael Hategan wrote:
> On Tue, 2007-10-09 at 13:22 +0000, Ben Clifford wrote:
>> The bit of kml that does the assignment is run in a sequential bit that 
>> sets up variables, before any of the parallel stuff happens (that usually 
>> consists of procedure calls, and is the part that ends up being evaluated 
>> in data dependency order rather than source text order).
>>
>> It makes sense to allow what you want to do, I think.
> 
> There was some discussion about removing the @ sign in front of built-in
> functions. There is no need for the distinction, and, apparently, it
> does cause problems.
> 
> 
>