Grégoire Dooms wrote:
> Very deep in the foundations of algorithms are the foundations of
> computer science semantics:
> http://en.wikipedia.org/wiki/Denotational_semantics
>
> An other area where I've been exposed ot fixed points is concurrent
> constraint programming where constraint propagat
Arthur wrote:
>Guess I am fishing for some exposition on the statement that the
>
>"The study of fixed points has been at the foundation of algorithms"
>
>
Very deep in the foundations of algorithms are the foundations of
computer science semantics:
http://en.wikipedia.org/wiki/Denotational_sem
Arthur wrote:
> re: "The study of fixed points has been at the foundation of algorithms"
>
> I guess what I am asking further is whether the statement is simply
> referencing the development of algorithms for solving the mathematical
> question of the fixed points of a function, in the context
Scott David Daniels wrote:
>Well, in fact both meanings of "fixed point" are used, seldom by the
>same person. I expect Knuth is in that small group that uses both
>meanings regularly (since his basic training was all mathematics).
>Look to the "functional programming" people for examination of t
Today was my 4th session in a sequence of nine.
I think the way it's developing for me is I hand out worksheets, which
pose questions around Python, and students have the option to just fill
them in, knowing Python "in their heads" well enough to not consult the
actual interpreter. Others run t
Maybe a tightening spam filter is to blame.
In any case, I'm resubscribing from my Gmail account.
As a Qwest user, I'm used to being discriminated against, thanks to the activities of my fellow Qwestians.
My next post will be back to business.
Kirby
Hi. This is the qmail-send program
Arthur wrote:
> I have thought of "fixed point" (in programming) as connected
> to/opposed to "floating point", not as something directly connected to
> the concept of "f(x)=x"
>
> The statement above seems to be telling me otherwise.
> Guess I am fishing for some exposition on the statement t
A bit of a windy road:
starting, as usual, with the personal frame of reference
PyGeo's current implementation supports the exploration of the geometry
of complex numbers, and therefore speaks Mobius transformations.
http://pygeo.sourceforge.net
now has a pretty picture of a simple recurs
