ugly package synopsis about glow HOT 4 CLOSED

Digging a bit deeper also shows that generated code is missing blank lines completely, for example a generated debug.go file

// Glow automatically generated OpenGL binding: http://github.com/go-gl/glow
package gl
import "C"
import "unsafe"
type DebugProc func(
    source uint32,
    gltype uint32,
    id uint32,
    severity uint32,
    length int32,
    message string,
    userParam unsafe.Pointer)
var userDebugCallback DebugProc
//export glowDebugCallback_glcore20
func glowDebugCallback_glcore20(
    source uint32,
    gltype uint32,
    id uint32,
    severity uint32,
    length int32,
    message *uint8,
    userParam unsafe.Pointer) {
  if userDebugCallback != nil {
    userDebugCallback(source, gltype, id, severity, length, GoStr(message), userParam)
  }
}

from glow.

shows that generated code is missing blank lines completely

For better or worse this is working as intended. Indeed the template output is filtered through BlankLineStrippingWriter largely to remove the huge amounts of hard-to-read whitespace that would otherwise be present in the generated files. There might be a clever middle ground but nothing I have yet bothered to implement.

from glow.

You're right. Looking at the code it's a much more complex issue than I originally thought. I am creating a simple solution that should give us nice package synopsis though, at least.

from glow.

@slimsag IMHO #41 is just opening a can of worms. I think a better solution is to scratch the BlankLineStrippingWriter altogether and fix the template. You can stop the template inserting eol with

bla{{/*
*/}}bla

and for the C typedefs re-implement Replace e.g. to

+func Replace(s, old, new string) string {
+       if s[:len(s)] != "\n" {
+               s+="\n"
+       }
+       return strings.Replace(s, old, new, -1)
+}

EDIT: created #44

from glow.