With some playing, I get to this, which gives me what I want for
downstream.
func DocComments(path string) (docs map[string]map[string][]*ast.Comment, err
error) {
fset := token.NewFileSet()
pkgs, err := parser.ParseDir(fset, path, nil, parser.ParseComments)
if err != nil
Yeah, possibly. Is there is way though to get the associated
ast.CommentGroup for a type's methods?
On Mon, 2016-09-26 at 20:59 -0700, Rob Pike wrote:
> It might be less disgusting to use text/scanner.
>
> -rob
--
You received this message because you are subscribed to the Google Groups
"gola
It might be less disgusting to use text/scanner.
-rob
On Mon, Sep 26, 2016 at 5:46 PM, Dan Kortschak <
dan.kortsc...@adelaide.edu.au> wrote:
> Is there a nicer way to do this than what I have here?
>
> func MethodDocComments(path string) (map[string]string, error) {
> fset := token.NewF
Is there a nicer way to do this than what I have here?
func MethodDocComments(path string) (map[string]string, error) {
fset := token.NewFileSet()
pkgs, err := parser.ParseDir(fset, path, nil, parser.ParseComments)
if err != nil {
return nil, err
}
I am trying to loop through a very large directory and build a list of
files from Palantir using a simple go filepath.Walk(). Thats it really.
Nothing complex... but it seems we have a memory leak or something?
Any ideas why this might be happening?
fatal error: unexpected signal during runtime
go/gocomments#TOC-Initialisms says initialisms or acronyms (e.g. "URL" or
"NATO") have a consistent case: URL or url.
But sometimes we have ToR (top-of-rack switch), QoS (quality of service),
or DoS (denial of service) that are commonly written with a combination of
upper- and lower-case letter
On Mon, 26 Sep 2016 00:06:11 PDT Asit Dhal wrote:
>
> I don't see any functions in Golang net/smtp package for CC and BCC.
> Does it support those functionalities ?
> If not, is there any work around for that ?
All of to, cc & bcc addresses from an email's headers must be
sent using RCPT comman
That code was written in 2010, while the specification for io.Writer was
written in 2009. Go 1.0 was released in 2012. Prior to Go 1.0, there wasn't
any strict compatibility agreement, so many things were in flux throughout
the code base. So, I assume that Brad added that check back then to hand
I am trying to create a new contact using the google contact api, however
its atom feed and XML. There doesn't seem to be a Golang library to do
this. I have got to here:
var c models.Category
c.Scheme = "http://schemas.google.com/g/2005#kind";
c.Term = "http://schemas.google.com/contact/200
On Mon, 26 Sep 2016 14:49:57 +
"Manuel Amador (Rudd-O)" wrote:
> > I don't see any functions in Golang net/smtp package for CC and
> > BCC. Does it support those functionalities ?
> > If not, is there any work around for that ?
>
> My RFC2822 knowledge is very rusty, but isn't that just a fu
On 09/26/2016 07:06 AM, Asit Dhal wrote:
> Hi,
> I don't see any functions in Golang net/smtp package for CC and BCC.
> Does it support those functionalities ?
> If not, is there any work around for that ?
My RFC2822 knowledge is very rusty, but isn't that just a function of
the MIME headers you
Hello, Gophers!
I am announcing the first iteration of curvetls: a Go library that
provides a robust framing and encryption layer for your Go programs,
striving to be secure, strict, and simple.
With curvetls, it's dead easy to go from raw sockets to secure channels,
based on CurveCP (NaCL) encry
Hi,
I don't see any functions in Golang net/smtp package for CC and BCC.
Does it support those functionalities ?
If not, is there any work around for that ?
--
You received this message because you are subscribed to the Google Groups
"golang-nuts" group.
To unsubscribe from this group and stop
I think you are overcomplicating things for yourself. Just use the solution
Jan has provided. If you don't want people to need to import time
additionally, re-export the constants from your own package. No need to
define a new type.
On Mon, Sep 26, 2016 at 11:17 AM, Ally Dale wrote:
> In final w
In final words, the KEY problem of my topic is:
It's easy to extending exists public types by redefine or use struct's
no-name embeding in Golang.
The new types will inherit all data and public methods from the old package.
But there is NO WAYS to inherit public consts and variables defined from
I think that is not a good idea.
First of all, I can't define these consts everywhere,so I have to create a
new package(eg:mytime) to define them.
And then, client package may use like this:
import(
"time"
".../mytime"
)
dur2WeeksAnd7Hours := mytime.Week*2+time.Hour*7
I think this code may make th
your questions don't make much sense without additional context. in particular
> this(fmt.Sprintf)
looks like a vague misunderstanding of how to avoid infinite recursion
in one's own Stringer interface implementation
(https://golang.org/pkg/fmt/#pkg-overview):
type X string
func (x X) St
i am new in go language. just i have questions
> thank u for answers
>>
>
On Sunday, September 25, 2016 at 10:12:58 AM UTC-7, hadies...@gmail.com
wrote:
>
> what is difference between in *fmt.Printf* function and *fmt.Sprintf* ???
>
>
--
You received this message because you are subscribed to t
I solved it by using ffmpeg:
inputDeviceName := "Microphone (Realtek High Definition Audio)"
outputFile := "recording.mp3"
cmd := exec.Command("C:/Dev/ffmpeg/bin/ffmpeg.exe", "-f","dshow",
"-i","audio=" + inputDeviceName, outputFile)
cmd.Stdout = os.Stdout
cmd.Stderr = os.Stderr
cmd.Stdin = os.
19 matches
Mail list logo
