pedromg

Keybase proof

I hereby claim:

• I am pedromg on github.
• I am pedromg (https://keybase.io/pedromg) on keybase.
• I have a public key ASAHu8RbaxCP59ycfkQTB4j1U0k8KcF7A2fmQXciodG-two

To claim this, I am signing this object:

pedromg

package main

import "fmt"

// fibonacci is a function that returns
// a function that returns an int.
func fibonacci() func() int {
	n_1, n := -1, 1
	return func() int {
		tmp := n

pedromg

package payment

import (
	"fmt"

	"appengine"
	"appengine/urlfetch"

	 "github.com/stripe/stripe-go"
	 "github.com/stripe/stripe-go/currency"

pedromg

package main

import "fmt"

type Person struct {
	Name string
	age  int // not Exported
}

func main() {

pedromg

import _ "net/http/pprof"

// If the app is not running an http server, one needs to start one:

go func() {
  log.Println(http.ListenAndServe("localhost:8000", nil))
}()

// Or else/then its just point the browser to:
// http://ip:port/debug/pprof/</code>

pedromg

configs.Data["smtp_host"]

pedromg

/* load configs. defaults to dev environment. */
func load_environment(e string) bool {
	var err error
	if e == "" {
		e = "dev"
	}
	configs, err = sstore.ReadFile("./configs/config_"+e+".sstore")
	if err != nil {
		return false
	}

pedromg

type SStore struct {
        Name     string
        Descr    string
        Data     map[string]string
}

pedromg

    def query(sql)
      sql += ';' unless sql.end_with?(';')
      # api call
      res = @bq_client.execute(
        :api_method => @bg_api.jobs.query,
        :body_object => { "query" => sql },
        :timeoutMs   => BQ_TIMEOUT,
        :parameters => { "projectId" => BQ_EPF_PROJECT_ID }
      )
      # return result

pedromg

http://commandcenter.blogspot.pt/2012/06/less-is-exponentially-more.html

"In the end of course it came out quite different from either C or C++. More different even
 than many realize. I made a list of significant simplifications in Go over C and C++:

    regular syntax (don't need a symbol table to parse)
    garbage collection (only)
    no header files
    explicit dependencies
    no circular dependencies