Revision 13 as of 2003-11-22 13:21:47

Clear message

See JohannesGijsbers for more on me, but I'm subscribed to this page, so you can leave me messages here.

Email: jlgijsbers at planet dot nl


So, if we had a nice pattern repository wiki, we could write about decorate-sort-undecorate there and link to it... {;D}= -- LionKimbro DateTime(2003-11-21T22:18:39Z)

PortlandPatternRepository? ;) -- JohannesGijsbers

Two thoughts:

I think that there is a type of pattern that people use within a procedure.

For an example of a basic one, there is the ForLoop.

But there are also others, like FirstTimeSeperate versus FirstTimeIntegrated.

That is, do you:

   1 first_time_a()
   2 always_b()
   3 first_time_c()
   4 always_d()
   5 
   6 while condition:
   7   always_b()
   8   always_d()

...or do you...

   1 first=1
   2 
   3 while condition:
   4     if first: first_time_a()
   5     always_b()
   6     if first: first_time_c()
   7     always_d()
   8     first=0

Surely, there are advantages to each one, no?

I taught beginning programmers for 2 years. I found that I didn't have words for a lot of things that I was trying to explain to them. Now I think I have the word for it: a "block pattern."

I think a site of block patterns would be interesting, and very beneficial for study by beginners.

DecorateSortUndecorate may be a block pattern. But maybe not- maybe it's an algorithmic pattern. But are they that different?

Speaking of algorithms- we need multiple algorithms wiki. {:)}=

Good talking with you. Feel free to delete whenever you like.

-- LionKimbro DateTime(2003-11-22T04:45:20Z)

Well, if I understand the code correctly, I would just do:

   1 first_time_a()
   2 first_time_c()
   3 while condition:
   4     always_b()
   5     always_d()

But that isn't really the point. What do you mean with a block pattern? It seems like another level of Scope (as in the DesignPatternsBook). -- JohannesGijsbers


CategoryHomepage

Unable to edit the page? See the FrontPage for instructions.