Rosetta Code:Village Pump/Task organization: Difference between revisions
Rosetta Code:Village Pump/Task organization (view source)
Revision as of 02:11, 10 November 2010
, 13 years agoApplied Template:vptopic
(Dynamically typed languages) |
(Applied Template:vptopic) |
||
| (2 intermediate revisions by 2 users not shown) | |||
Line 1:
{{Vptopic
|topic=Task organization
|summary=Restructuring tasks.
}}
==Type algebra==
'''Further restructuring'''. I propose to group the tasks related to the language ''types algebra'' under this category, like it was done with control flow statements. A types algebra is a set of predefined types and the operations constructing new types out of given ones. For example, the array type is produced by such an operation. It takes the type of the index, the type of the element and produces a new container type called array. Here is an incomplete list of algebraic operations most common to higher-level typed languages:
Line 26 ⟶ 31:
:Dynamically typed languages have a types algebra as well, obviously. The difference if any, is that some of the algebraic operations become proper functions as well as the types. I.e. you can construct an array type at run-time, type is a first class object, etc. --[[User:Dmitry-kazakov|Dmitry-kazakov]] 09:58, 24 February 2009 (UTC)
==Stirring up old ideas==
So we had a sort of organized task category tree before at [[:Category|Solutions by Programming Task]]. Right now people are directed to the flat list in the sidebar. Do we want to organize the tasks with categories anymore? I think new users might have a hard time dealing with the flat list, but maybe they don't go there first. Is there a SMW way to organize the tasks? Ideas? --[[User:Mwn3d|Mwn3d]] 19:06, 16 October 2010 (UTC)
| |||