Talk:Array slicing

This article is within the scope of WikiProject Computing, a collaborative effort to improve the coverage of computers, computing, and information technology on Wikipedia. If you would like to participate, please visit the project page, where you can join the discussion and see a list of open tasks.ComputingWikipedia:WikiProject ComputingTemplate:WikiProject ComputingComputing articles

???

This article has not yet received a rating on the project's importance scale.

This article is supported by WikiProject Computer science.

Things you can help WikiProject Computer science with:

Here are some tasks awaiting attention:

Article requests :
- Requested articles/Applied arts and sciences/Computer science, computing, and Internet
Cleanup :
- Computer science articles needing attention
- Computer science articles needing expert attention
Copyedit :
- Computing
Expand :
- Computer science
Infobox :
- Computer science articles without infoboxes
Maintain :
- Timeline of computing 2020–present
Photo :
- Find pictures for the biographies of computer scientists (see List of computer scientists)
- Computing articles needing images
Stubs :
- Computer science stubs
Unreferenced :
- WikiProject Computer science/Unreferenced BLPs
Project-related :
- Tag all relevant articles in Category:Computer science and sub-categories with {{WikiProject Computer science}}

Array slicing survived Wikipedia:VFD. See: Wikipedia:Votes for deletion/Array slicing -- Wile E. Heresiarch 06:27, 25 Jun 2004 (UTC)

I'm interested in seeing a discussion of the implementation of the internal implementation (data structures) used for array slicing, especially in the multi-dimensional and dynamic array scenarios. Dataphile 00:14, Aug 15, 2004 (UTC)

Another interesting aspect to be mentioned here is the difference between 0-based and 1-based languqages. Typically in 0-based environments, slicing functions/methods take two args, the first for the first element to be returned, and a second index-arg that usually specifies 1 number higher than the last element to be extracted. There is quite a bit of info on this subject, as a google on slicing "0-based" "1-based" shows. 141.152.253.15 17:21, 19 November 2005 (UTC)[reply]

Just a question, but in the Fortran 90 section, should PRINT statements be used? I know that PRINT isn't obsolete or deprecated, but I was always taught that WRITE is the "correct" method of output because it can output to more than standard output, which is all PRINT can do, and that WRITE allows use of the extra options (ADVANCE, etc.) TheMatt (talk) 17:34, 8 October 2009 (UTC)[reply]

Slices in Fortran 66

This section is still wrong. The code in the example is Fortran 77, not Fortran 66 which did not let you do (*) dimensions or * default formats or PARAMETER statements. I'd move that example to the F77 section and put in something that used the standard DIMENSION VEC(1) for variable length arguments. John L (talk) 18:46, 4 December 2016 (UTC)[reply]

This section is wrong. First, arrays are stored by column in Fortran, so the example is a column slice, not a row slice. But row slices are very easy, you have just to pass an increment along the array and its length. A fairly common trick in libraries, like BLAS. Fustis (talk) 19:08, 29 September 2014 (UTC)[reply]