Rosetta Code talk:TODO: Difference between revisions

From Rosetta Code
Content added Content deleted
(string merge)
(New section: HOPL)
Line 3: Line 3:
String Byte Length and String Character Length were split because many examples in String Length didn't differentiate between 8-bit characters and wide characters, which is an important distinction for low-level languages on modern systems. If they get merged, this distinction needs to be preserved. --[[User:Short Circuit|Short Circuit]] 13:20, 2 December 2007 (MST)
String Byte Length and String Character Length were split because many examples in String Length didn't differentiate between 8-bit characters and wide characters, which is an important distinction for low-level languages on modern systems. If they get merged, this distinction needs to be preserved. --[[User:Short Circuit|Short Circuit]] 13:20, 2 December 2007 (MST)
:Agreed. Currently, many of the string tasks have the same code between the two pages, so you can't tell which one is correct for each page. Once merged, there won't be duplication, and we can tag the language with only one string operation with the "incorrect" template. --[[User:IanOsgood|IanOsgood]] 09:08, 3 December 2007 (MST)
:Agreed. Currently, many of the string tasks have the same code between the two pages, so you can't tell which one is correct for each page. Once merged, there won't be duplication, and we can tag the language with only one string operation with the "incorrect" template. --[[User:IanOsgood|IanOsgood]] 09:08, 3 December 2007 (MST)

== HOPL ==

Does the HOPL have a regular URL pattern that we can take advantage of with the links? It's very slow to load and difficult to find these relevant pages. --[[User:Mwn3d|Mwn3d]] 21:06, 2 March 2008 (MST)

Revision as of 04:06, 3 March 2008

I can do the headers...I've already started sort of. --mwn3d 15:00, 11 November, 2007

String Length

String Byte Length and String Character Length were split because many examples in String Length didn't differentiate between 8-bit characters and wide characters, which is an important distinction for low-level languages on modern systems. If they get merged, this distinction needs to be preserved. --Short Circuit 13:20, 2 December 2007 (MST)

Agreed. Currently, many of the string tasks have the same code between the two pages, so you can't tell which one is correct for each page. Once merged, there won't be duplication, and we can tag the language with only one string operation with the "incorrect" template. --IanOsgood 09:08, 3 December 2007 (MST)

HOPL

Does the HOPL have a regular URL pattern that we can take advantage of with the links? It's very slow to load and difficult to find these relevant pages. --Mwn3d 21:06, 2 March 2008 (MST)