Talk:Executable library: Difference between revisions
Content added Content deleted
(→Pike problem: It needs to be one file.) |
|||
Line 58: | Line 58: | ||
: --[[User:Paddy3118|Paddy3118]] 02:24, 6 August 2011 (UTC) |
: --[[User:Paddy3118|Paddy3118]] 02:24, 6 August 2011 (UTC) |
||
::Ah, I get it now. The hailstone example serves two purposes: borrow from another RC article, avoiding duplication; and present a useful example of API/CLI bundling. My ScriptedMain examples do not offer a practical reason for their existence. However, I think that the hailstone sequence is a bit much for coders who just want the Executable library behavior. Maybe use Hello World instead? I see now that it's hard to strike a balance between simplicity and usefulness. Do you have more suggestions for RC-ifying my submissions? --[[User:Mcandre]] |
::Ah, I get it now. The hailstone example serves two purposes: borrow from another RC article, avoiding duplication; and present a useful example of API/CLI bundling. My ScriptedMain examples do not offer a practical reason for their existence. However, I think that the hailstone sequence is a bit much for coders who just want the Executable library behavior. Maybe use Hello World instead? I see now that it's hard to strike a balance between simplicity and usefulness. Do you have more suggestions for RC-ifying my submissions? --[[User:Mcandre]] |
||
==Pike problem== |
|||
''"to use the library as a class, save it as HailStone.pike to use it as a module, save it as Hailstone.pmod "'' is not what the task is after. Make it one file and your on! --[[User:Paddy3118|Paddy3118]] 07:34, 7 November 2011 (UTC) |