This issue may be of interest to you:
https://github.com/golang/go/issues/10958
On Tuesday, September 20, 2016 at 7:42:24 PM UTC-7, Tony Chen wrote:
>
> ### What version of Go are you using (`go version`)?
> go 1.6.2 mac/amd64
>
> ### What operating system and processor architecture are you using
@Jan: that does not work; I used this example:
http://nerdyworm.com/blog/2013/05/15/sorting-a-slice-of-structs-in-go/
@xao: slight change: when using sort.Sort(Courses(courses)) it does work!
Thanks to you both! Here is the working version:
https://play.golang.org/p/GZXzM4ghNX
2016-09-20 22:14 G
Hi,
I have started using https://godoc.org/github.com/jung-kurt/gofpdf
So far I can get some output, but everything is overlapping each other at
the start of the page.
I am using Cell or Text for writing a line of output.
How can I advance to the next physical "row" (line) in the output page?
Well adding some code would help. But generally there is a ln variable you need
to set to 1 to break the line.
Your really need to read the docs carefully to get what you want with gofpdf.
Most of the info is there.
--
You received this message because you are subscribed to the Google Groups
https://github.com/xudongzheng/gitstreak
I decided to write this a few weeks ago to keep track of my own progress,
after having read
http://lifehacker.com/281626/jerry-seinfelds-productivity-secret months
ago. Go related feedback in particular would be appreciated. Hope some of
you find this u
Any kind of computational geometry code will have subtle issues in just this
area. Broadly, the issue is classification of a point or line as IN, OUT, or
ON. Of these, ‘ON’ is the difficult one because floating point prevents perfect
calculation where real numbers would allow it. This is because
Hi
I'm currently writing a program which listens to a HID (sliders and
buttons) and controls a karaoke program with these inputs. Grabbing input
and sending commands with websockets work, but now I need to record the
audio output as well.
I tried to compile and run portaudio, but I cannot inst
Hi All,
I am new to golang. I have been trying to build golang 1.5.0 with golang
1.4.2 bootstrap binaries. My build host is centos5 and build is yocto
build. But I always get below compilation issue.
# Building Go bootstrap tool.
| cmd/dist
| go build
_/local/jenkins/ws/CB/160921103249-br
Centos 5 is not supported, the kernel is too old. Sorry.
--
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 golang-nuts+unsubscr...@googlegroups.com.
For more optio
Or if you have them as actual constants, 355.0 / 113
On Monday, September 19, 2016 at 12:07:13 PM UTC-6, Hotei wrote:
>
> I think you'll need something like x := float(355) / float(113) - where
> float is either float32 or float64 depending on your preferred trade-off
> for accuracy vs bytes r
Hi all, I am working for DeviceAtlas, the mobile detection solution and
know some users of the C enterprise API available here
https://deviceatlas.com/deviceatlas-haproxy-module were wondering how to
integrate it inside golang. Can be taken as it is or at least as an
inspiration as I m not ne
Hi, folks.
Recently i've watched Rick Hudsons presentation about beating latency
problem in Go GC and it was great,
but when i've tried to understand how does it works i've concluded that
there are not so much info compare to Java for example.
Design docs and source code looks complicated t
Yes thanks.
I decided on catching the missed ON (edge/corner) case at the end of the
function with an extra if statement when the numerical work returns
EXITS_BOX=true, ENTERS_BOX=false - then I do a relatively simple check for
the 'ray' outside the box - if Ray.Origin was outside and EXITS_BO
I believe, that as the go gc is relatively rapidly developing, writing a
book about it is going to give you some grief, as the information in it
will likely be out of date by the time it comes out. The same goes, to
varying degrees, for other kind of documentation.
There are several talks Rick Hud
Thx Ed, Ln() is exactly what I need!
2016-09-21 12:51 GMT+02:00 Ed Pelc :
> Well adding some code would help. But generally there is a ln variable you
> need to set to 1 to break the line.
>
> Your really need to read the docs carefully to get what you want with
> gofpdf. Most of the info is ther
hey all,
Today ARM announced a new real time chip for cars.
http://www.anandtech.com/show/10690/arm-announces-the-cortexr52-cpu-deterministic-safe-for-adas-more
https://github.com/golang/go/wiki/GoArm
I am curious how hard it would be for golang to target this ??
Not that i would be anytime so
I want to start developing for Android, and would like your advice on that:
Where to start.
My background is Linux. I have a lot of programming experience. Mainly C
and Perl, followed by C and Python, and for the last five years it's mainly
Go. I did some Java programming for a few weeks, decad
You could also use
https://equinox.io/
once you have your token. keys, etc all setup, you can build new releases
rpm, deb, etc using
equinox release \
--version="1.0.0" \
--platforms="darwin_amd64 linux_amd64" \
--signing-key=/Users/inconshreveable/equinox.key \
--app="app_ja6WuaZgwsF" \
--to
Le mardi 20 septembre 2016 17:17:37 UTC+2, mhhcbon a écrit :
>
> Hi,
>
> on my way to learn to use pprof, i now face some intriguing results with
> lots of runtime.* calls,
>
> can you help me to understand what those call are and how i should care
> about ?
>
> (pprof) top30
> 8720ms of 14380
Hi,
thanks again for all the explanations.
I kept digging, and now i m having the same behavior as this thread
https://groups.google.com/forum/#!topic/golang-nuts/P1EFc4kMBfo
I run test with memprofile enabled, then use pprof to see the results, but
the numbers are all 0.
$ go test -v -bench=
... Sorry for the publishing issues..
// BytesByLine emits chunks of []byte splitted by line (\n).
func BytesByLine() *Transform {
var buf []byte
var EOL = []byte("\n")
byLine := func () [][]byte {
ret := make([][]byte, 0)
lines := bytes.Split(buf, EOL)
isEOL := len(buf)>0 && b
On Wed, Sep 21, 2016 at 7:16 AM, Ged Wed wrote:
>
> Today ARM announced a new real time chip for cars.
>
> http://www.anandtech.com/show/10690/arm-announces-the-cortexr52-cpu-deterministic-safe-for-adas-more
>
> https://github.com/golang/go/wiki/GoArm
>
> I am curious how hard it would be for gola
Thanks for the response. That's an amazing testament to Yolanda design.
I guess it's just a matter of a board coming out with it on now and then
having a crack at it
On Wed, 21 Sep 2016, 19:54 Ian Lance Taylor, wrote:
> On Wed, Sep 21, 2016 at 7:16 AM, Ged Wed wrote:
> >
> > Today ARM announce
Please can someone can enlighten me or point me towards relevant docs/other
regarding the design decisions behind time.Time?
Specifically why the concept of an instant in time, referenced many times
throughout the time docs, was not encoded as a type itself:
type Instant struct {
sec int64
On Wed, Sep 21, 2016 at 11:22 AM, Paul Jolly wrote:
> Please can someone can enlighten me or point me towards relevant docs/other
> regarding the design decisions behind time.Time?
>
> Specifically why the concept of an instant in time, referenced many times
> throughout the time docs, was not enc
Your Instant is not an Instant, it's a duration. For a duration to
demarkate an Instant, you'd actually need a reference point (a zero). And
that'll pretty much certainly be given relative to a location. So even your
Instant still has a location, it's just implied (probably to be UTC).
Personally,
The sec and nsec fields in a time.Time are relative to the Unix epoch and
so denote a point in time by themselves. The location is merely for
presentation.
ons 21 sep. 2016 kl 20:35 skrev 'Axel Wagner' via golang-nuts <
golang-nuts@googlegroups.com>:
> Your Instant is not an Instant, it's a durat
Michael is of course correct about floating point but it is possible to
robustly handle cases like this. I'm not sure on your exact goals but
you've not already seen there are several papers about robust ray-box
intersection e.g. An Efficient and Robust Ray-Box Intersection Algorithm by
Amy Wil
On Wed, Sep 21, 2016 at 11:55 AM, Jakob Borg wrote:
> The sec and nsec fields in a time.Time are relative to the Unix epoch and so
> denote a point in time by themselves. The location is merely for
> presentation.
Pedantically, they are not relative to the Unix epoch. They are
relative to Januar
Ah, indeed. No pedantry required to appreciate the difference, it's almost
two thousand years after all. :) Sorry for the confusion.
//jb
ons 21 sep. 2016 kl 21:40 skrev Ian Lance Taylor :
> On Wed, Sep 21, 2016 at 11:55 AM, Jakob Borg wrote:
> > The sec and nsec fields in a time.Time are relat
On Wed, Sep 21, 2016 at 1:55 PM, Jakob Borg wrote:
> The sec and nsec fields in a time.Time are relative to the Unix epoch and so
> denote a point in time by themselves.
Right, making your "instant" a duration with an implicit starting
time, and a time that has a timezone at that (aka, just a dur
I am aware. I don't understand how that contradicts my point that they have
an implied location (or rather *Location, namely time.UTC).
I am aware, that you could choose an arbitrary *Location (because that's
what time.UTC is. Just one, arbitrary, timezone) and create a special
in-memory Represent
>
> > The sec and nsec fields in a time.Time are relative to the Unix epoch
> and so
> > denote a point in time by themselves. The location is merely for
> > presentation.
>
> Pedantically, they are not relative to the Unix epoch. They are
> relative to January 1, year 1, 00:00:00.0
UTC, Coordinated Universal Time, is not really an arbitrary time zone. It's
the time scale underlying almost all time measurements on Earth (excepting
some specific use cases, typically in astronomy) and from which all time
zones are derived. As such, I don't think it implies a location (other than
Thanks for those links - I started using a something similar to what is
described as Smit's algorithm (Slab method) in the Amy Williams paper. My
code us subtly different to that usually given because I check the "back
face" intersection first -for an early terminate ; this basically involves
s
This was a great find, I am doing the same now in Windows. I've had to
modify it a bit, I imagine weather.gov has changed the image somewhat since
the original post in 2013. I've had to remove some more of the light blue
colors and then one more pass to get rid of the light grey radar "noise".
I have a go binary that calls C code (with cgo). It is a little test, and
main calls google.Init() and calls some C function that ends up opening a
local file.
I get an error like:
WARNING: Logging before InitGoogle() is written to STDERR
E0921 15:16:46.570978 184662 extractor.cc:102]
generic:
On 22 September 2016 at 05:54, Ian Lance Taylor wrote:
> On Wed, Sep 21, 2016 at 7:16 AM, Ged Wed wrote:
> >
> > Today ARM announced a new real time chip for cars.
> >
> > http://www.anandtech.com/show/10690/arm-announces-the-
> cortexr52-cpu-deterministic-safe-for-adas-more
> >
> > https://gith
On Sun, Sep 18, 2016 at 1:57 PM, wrote:
> It looked like I would have to use pkg unsafe
BTW, you don't have to use package unsafe. Use package math's
Float32bits and Float32frombits functions.
--
You received this message because you are subscribed to the Google Groups
"golang-nuts" group.
To
I wonder if go's google.Init() ends up missing initializers that are in the
C side of cgo.
On Wednesday, September 21, 2016 at 3:44:20 PM UTC-7, matu...@google.com
wrote:
>
> I have a go binary that calls C code (with cgo). It is a little test, and
> main calls google.Init() and calls some C f
Good point. I missed that. Also, I did not mean “unsolvabe” just not solvable
using slightly a different precision.
Common solutions:
Remove the divides by multiplying them out. Then it just works (at least in FP
where integer precision is not such an issue as in graphics hardware)
Avoid the c
On Wed, Sep 21, 2016 at 1:41 AM, AnomalRoil wrote:
> So here am I: should I open an issue for a trivial sign mistake in a
> sentence in the documentation?
Opening an issue would have been fine. In this case, though, I just
sent the trivial change out for review:
https://go-review.googlesource.com
On Thu, Sep 22, 2016 at 12:33 AM, Peter Kleiweg wrote:
> How about Go Mobile? Is that useful as a starting point, or should I try to
> get to know the system first using Android Studio? What are the capabilities
> of Go Mobile? Can it do all the stuff a native app can do, system calls,
> events, g
43 matches
Mail list logo