Talk:Floyd's triangle: Difference between revisions

From Rosetta Code
Content added Content deleted
(→‎Output: Intuitive?)
Line 11: Line 11:


: The current format requirement may be rigorous, but not intuitive. You go through all this trouble to align digits, yet because widths of numbers vary within each line, the slanted right edge of the triangle is not a straight line and looks unpleasant. What's the point of the complicated formatting, really? --[[User:Ledrug|Ledrug]] 23:03, 25 June 2012 (UTC)
: The current format requirement may be rigorous, but not intuitive. You go through all this trouble to align digits, yet because widths of numbers vary within each line, the slanted right edge of the triangle is not a straight line and looks unpleasant. What's the point of the complicated formatting, really? --[[User:Ledrug|Ledrug]] 23:03, 25 June 2012 (UTC)

:: Partially a reaction to the issues seen in [[Pascal's triangle]] where there was not enough rigor. No doubt someone could still find a way to adhere to the letter of the task rather than the spirit, but that too could be interesting to see. (I pity the people that have to write documentation for their work who don't try doing something similar for an open source type project where lessons learned can be rapid and sometimes brutal, but on RC - kind-a nice).
:: Partially because some specs are just as particular; with non-intuitive requirements that are even more hidden. --[[User:Paddy3118|Paddy3118]] 02:07, 26 June 2012 (UTC)

:: P.S. Should I add an optional goal: ''to add an option to your routine that can produce equi-width columns'' ? --[[User:Paddy3118|Paddy3118]] 02:07, 26 June 2012 (UTC)

Revision as of 02:07, 26 June 2012

Inspiration

I need to add a link to Vihart.

Can the colour of the font of just the task description be changed to pink? (A Dark side of the moon joke). --Paddy3118 19:13, 24 June 2012 (UTC)

Output

  • Has to be shown
  • Has to be formatted just-so.
    --Paddy3118 19:17, 24 June 2012 (UTC)

I am changing the output from print n=5 and n=15 to n=5 and n=14 to highlight the case of what should be done when the number of digits in the numbers of the last row changes, and is not the last digit itself. In this case, column widths need to change. Sorry Go language (but thanks for the quick example). The reason is, that I am trying to be more rigourous about the output format than in Pascal's triangle. --Paddy3118 06:52, 25 June 2012 (UTC)

The current format requirement may be rigorous, but not intuitive. You go through all this trouble to align digits, yet because widths of numbers vary within each line, the slanted right edge of the triangle is not a straight line and looks unpleasant. What's the point of the complicated formatting, really? --Ledrug 23:03, 25 June 2012 (UTC)
Partially a reaction to the issues seen in Pascal's triangle where there was not enough rigor. No doubt someone could still find a way to adhere to the letter of the task rather than the spirit, but that too could be interesting to see. (I pity the people that have to write documentation for their work who don't try doing something similar for an open source type project where lessons learned can be rapid and sometimes brutal, but on RC - kind-a nice).
Partially because some specs are just as particular; with non-intuitive requirements that are even more hidden. --Paddy3118 02:07, 26 June 2012 (UTC)
P.S. Should I add an optional goal: to add an option to your routine that can produce equi-width columns ? --Paddy3118 02:07, 26 June 2012 (UTC)