tags:

views:

459

answers:

5

I'm having a little play with google's Go language, and I've run into something which is fairly basic in C but doesn't seem to be covered in the documentation I've seen so far

When I pass a pointer to an array to a function, I presumed we'd have some way to access it as follows:

func conv(x []int, xlen int, h []int, hlen int, y *[]int)

    for i := 0; i<xlen; i++ {
        for j := 0; j<hlen; j++ {
            *y[i+j] += x[i]*h[j]
        }
    }
 }

But the Go compiler doesn't like this:

sean@spray:~/dev$ 8g broke.go
broke.go:8: invalid operation: y[i + j] (index of type *[]int)

Fair enough - it was just a guess. I have got a fairly straightforward workaround:

func conv(x []int, xlen int, h []int, hlen int, y_ *[]int) {
    y := *y_

    for i := 0; i<xlen; i++ {
        for j := 0; j<hlen; j++ {
            y[i+j] += x[i]*h[j]
        }
    }
}

But surely there's a better way. The annoying thing is that googling for info on Go isn't very useful as all sorts of C\C++\unrelated results appear for most search terms.

A: 

the semicolon and the asterisk are added and removed.

*y[i+j] += x[i]*h[j]
-->
(*y)[i+j] += x[i] * h[j];

Behrooz
In Go you can skip the semicolon, and the asterisk was how I thought a pointer to an array should be used.
Sean
Drop the semicolon. From Release 2009-12-22:Since the last release there has been one large syntactic change tothe language, already discussed extensively on this list: semicolonsare now implied between statement-ending tokens and newline characters.See http://groups.google.com/group/golang-nuts/t/5ee32b588d10f2e9 fordetails.
peterSO
+2  A: 

The Google Go docs state the following about passing arrays - they say you usually want to pass a slice (instead of a pointer?):

Updated:

As indicated by @Chickencha's comment, array slices are references which is why they are efficient for passing. Therefore likely you will want to use the slice mechanism instead of "raw" pointers.

From Google Effective Go doc http://golang.org/doc/effective_go.html#slices

Slices are reference types,


Original

It's under the heading

An Interlude about Types

[...snip...] When passing an array to a function, you almost always want to declare the formal parameter to be a slice. When you call the function, take the address of the array and Go will create (efficiently) a slice reference and pass that.

Using slices one can write this function (from sum.go):

09    func sum(a []int) int {   // returns an int
10        s := 0
11        for i := 0; i < len(a); i++ {
12            s += a[i]
13        }
14        return s
15    }

and invoke it like this:

19        s := sum(&[3]int{1,2,3})  // a slice of the array is passed to sum    

Maybe pass the whole array as a slice instead. Google indicates Go deals efficiently with slices. This is an alternate answer to the question but maybe it's a better way.

John K
I agree that this sounds like the way to go. A slice is basically a pointer to an array already and is the preferred way of passing an array by reference.
Evan Shaw
+1  A: 

The length is part of the array's type, you can get length of an array by the len() built-in function. So you needn't pass the xlen, hlen arguments.

In Go, you can almost always use slice when passing array to a function. In this case, you don't need pointers. Actually, you need not pass the y argument. It's the C's way to output array.

In Go style:

func conv(x, h []int) []int {
    y := make([]int, len(x)+len(h))
    for i, v := range x { 
        for j, u := range h { 
            y[i+j] = v * u 
        }   
    }   
    return y
}

Call the function:

conv(x[0:], h[0:])
Stephen Hsu
The value of i is 0 to (len(x)-1) and the value of j is 0 to (len(h)-1). Therefore, the value of (i+j) is 0 to ((len(x)-1)+(len(h)-1)). Since array indices start at zero, don't we need ((len(x)-1)+(len(h)-1)+1) array elements for y?
peterSO
For `var s []int`, the references `s`, `s[0:len(s)]`, and `s[0:]` are all the same thing, the slice `s`. So, more concisely, write `conv(x, h)`, instead of `conv(x[0:], h[0:])`.
peterSO
+1  A: 

Here's a working Go program.

package main

import "fmt"

func conv(x, h []int) []int {
    y := make([]int, len(x)+len(h)-1)
    for i := 0; i < len(x); i++ {
        for j := 0; j < len(h); j++ {
            y[i+j] += x[i] * h[j]
        }
    }
    return y
}

func main() {
    x := []int{1, 2}
    h := []int{7, 8, 9}
    y := conv(x, h)
    fmt.Println(len(y), y)
}

To avoid wrong guesses, read the Go documentation: The Go Programming Language.

peterSO
A: 

Types with empty [], such as []int are actually slices, not arrays. In Go, the size of an array is part of the type, so to actually have an array you would need to have something like [16]int, and the pointer to that would be *[16]int. So, what you are actually doing already is using slices, and the pointer to a slice, *[]int, is unnecessary as slices are already passed by reference.

Also remember that you can easily pass a slice referring to the entire array with &array (as long as the element type of the slice matches that of the array).

Example:

package main
import "fmt"

func sumPointerToArray(a *[8]int) (sum int) {
    for _, value := range *a { sum += value }
    return
}
func sumSlice (a []int) (sum int) {
    for _, value := range a { sum += value }
    return
}
func main() {
    array := [...]int{ 1, 2, 3, 4, 5, 6, 7, 8 }
    slice := []int{ 1, 2, 3, 4 }
    fmt.Printf("sum arrray via pointer: %d\n", sumPointerToArray(&array))
    fmt.Printf("sum array via slice: %d\n", sumSlice(&array))
    fmt.Printf("sum slice: %d\n", sumSlice(slice))
    slice = &array
    fmt.Printf("sum slice: %d\n", sumSlice(slice))
}
Arkku
Oh, as an additional note, the [...] notation for the length of an array can only be applied to array literals to make the compiler count the elements for you. One cannot, for example, have a *[...]int as the formal argument of a function.
Arkku