Talk:Hello world/Text

Some examples lack some parts of the code. e.g. the Java example is not a complete program.

It's not uncommon for RC tasks to exclude code that represents the program surrounding the code. This helps make it obvious what code is specific to the task at hand. If you need to see what the surrounding code looks like, see Empty Program. --Short Circuit 02:31, 21 November 2008 (UTC)

Sometimes, it's necessary to show the complete program. For instance, say a task is to set a variable to 2.5 --- showing the statement J = 2.5 by itself in most languages would probably be wrong as (most?) languages would like/need/require some sort of declaration of the type of variable it is (and/or other attribute thingys), and that's the sticky wicket part. Just showing the assignment of the variable would do a disservice. I like to see what various languages need for a prologue.-- Gerard Schildberger 18:14, 11 August 2012 (UTC)

Hello World

I don't care to be cliché (Hence why I originally wrote the text as "Goodbye World"), but in light of confusion like this (and I've seen others mention it elsewhere), perhaps the task should be renamed to Hello World - text, and the relevant output strings adjusted? Similar would need to be said for the GUI task. Any objections? --Michael Mol 03:39, 20 January 2010 (UTC)

Audible Hello World?

I'd like to see a "Hello World/Audible" or "Hello World/Spoken" task here. The only task representing text-to-speech (which is common in accessibility aids and a large field) is "Using a speech engne to highlight words" - a draft task with one implementation (mine). That task would benefit from having a simpler text-to-speech task. I think it would be nice to have another Hello World as well. I know of 4 languages off the top of my head which I can write examples in. Thoughts? --Crazyfirex 03:06, 18 September 2011 (UTC)

There is an audible version: http://rosettacode.org/wiki/Speech_synthesis Markhobley 10:03, 18 September 2011 (UTC)