[go-nuts] Architectural question

2017-10-07 Thread max
Hi, i am challenged to develop an effective failover mechanism of aggregated notification of certain transactions. I have transactions by merchant. Every hour i need to send email (and some other) notifications, aggregated by the merchants to specific recipients. Now i am doing it with

Re: [go-nuts] [ANN] 99c

2017-10-07 Thread Devon H. O'Dell
(I’d love to contribute, mostly “99c is a c99 compiler” made me wonder if c99 was a requirement. Sorry for inbox spam.) On Sat, Oct 7, 2017 at 7:45 PM Devon H. O'Dell wrote: > More curiosity than anything, was just wondering whether patches to make > it c11 (or c2x

Re: [go-nuts] [ANN] 99c

2017-10-07 Thread Devon H. O'Dell
More curiosity than anything, was just wondering whether patches to make it c11 (or c2x whenever that happens) would be accepted :) On Sat, Oct 7, 2017 at 6:42 PM Jan Mercl <0xj...@gmail.com> wrote: > Do you have any particular feature(s) of C11 on your mind? Because maybe > some of them are

[go-nuts] important

2017-10-07 Thread 王晚成
hello， What is the meaning of the mstartfn field inside the M structure under runtime2.go? Goroutine is eventually executed by threads, which naturally require the mstartfn function to obtain G tasks. That's correct, isn't it? Thanks very much. -- You received this message because you are

Re: [go-nuts] [ANN] 99c

2017-10-07 Thread Jan Mercl
Do you have any particular feature(s) of C11 on your mind? Because maybe some of them are possibly easy to add. Also, IIRC, one or two are already there, just disabled by default, so adding support of the -std flag can make them available. On Sun, Oct 8, 2017, 01:37 Devon H. O'Dell

Re: [go-nuts] [ANN] 99c

2017-10-07 Thread Devon H. O'Dell
Is there any desire to support c11? On Sat, Oct 7, 2017 at 1:01 PM Jan Mercl <0xj...@gmail.com> wrote: > Command 99c is a c99 compiler targeting a virtual machine: > https://github.com/cznic/99c > > > > -- > > -j > > -- > You received this message because you are subscribed to the Google Groups >

Re: [go-nuts] Printing unexported fields

2017-10-07 Thread Ian Lance Taylor
On Sat, Oct 7, 2017 at 2:19 PM, wrote: > > fmt.Printf appears to access unexported fields fine, how does this work? In > this example, the call to Printf finds the field name of 'a' and shows the > value. It uses the reflect package (https://golang.org/pkg/reflect), which

[go-nuts] Printing unexported fields

2017-10-07 Thread uluyol0
fmt.Printf appears to access unexported fields fine, how does this work? In this example , the call to Printf finds the field name of 'a' and shows the value. -- You received this message because you are subscribed to the Google Groups "golang-nuts"

[go-nuts] [ANN] 99c

2017-10-07 Thread Jan Mercl
Command 99c is a c99 compiler targeting a virtual machine: https://github.com/cznic/99c -- -j -- You received this message because you are subscribed to the Google Groups "golang-nuts" group. To unsubscribe from this group and stop receiving emails from it, send an email to

Re: [go-nuts] binary.Read()

2017-10-07 Thread Jan Mercl
On Sat, Oct 7, 2017 at 8:48 PM Johan terryn wrote: > If I declare "in" as var of type os.File before the call to binary.read(...) > I get a compile error stating that in is not a reader, without the declaration it works fine... > just odd unexpected behavior. Why not

Re: [go-nuts] binary.Read()

2017-10-07 Thread Johan terryn
If I declare "in" as var of type os.File before the call to binary.read(...) I get a compile error stating that in is not a reader, without the declaration it works fine... just odd unexpected behavior. Johan On Thursday, October 5, 2017 at 9:16:18 PM UTC+2, Jan Mercl wrote: > > On Thu, Oct

Re: [go-nuts] Are all running goroutines killed when main ends?

2017-10-07 Thread David Collier-Brown
On Friday, October 6, 2017 at 9:49:18 AM UTC-4, Michael Jones wrote: > > Imagine the slightly stronger notion of a "will" as in a person's last > will and testament. Actions in your will are steps to be carried out in the > event of your death. Presumably if an action has already been done

[go-nuts] Re: Variable scope for text/template

2017-10-07 Thread silviucapota
Hein, you can try passing a function to the template. That is, a function which de-normalizes your person struct into an ad-hoc Num + Name record See here: https://play.golang.org/p/1XIIO-0lcu Cheers Silviu On Friday, 6 October 2017 01:22:49 UTC-4, Hein Meling wrote: > > Hi all, > > Please see

Re: [go-nuts] Are all running goroutines killed when main ends?

2017-10-07 Thread Michael Jones
Agree with Lucio and Bakul on each point. It is not something I need...just raising the observation that one could imagine "defer until even later" and it is an interesting thought experiment. On Sat, Oct 7, 2017 at 1:59 AM, Bakul Shah wrote: > > If a process is killed by

[go-nuts] Re: Variable scope for text/template

2017-10-07 Thread Simon Ritchie
AFAIK a template can only access the structure that's passed to to it. It can't get at any of the other variables of the Go function that executes it, global or local. All it can do is render the data in the structure that's passed to it. On Friday, October 6, 2017 at 6:22:49 AM UTC+1, Hein

Re: [go-nuts] Are all running goroutines killed when main ends?

2017-10-07 Thread Bakul Shah
If a process is killed by the kernel for some reason (or kill -9) none of these cleanup functions will run. The last will idea is meaningful only when the main() dies and doesn't care to wait for all the other goroutines to die a clean death. But in this case you are in essence passing a

Re: [go-nuts] Are all running goroutines killed when main ends?

2017-10-07 Thread Lucio
On Friday, 6 October 2017 15:49:18 UTC+2, Michael Jones wrote: > > Imagine the slightly stronger notion of a "will" as in a person's last > will and testament. Actions in your will are steps to be carried out in the > event of your death. Presumably if an action has already been done during >