|| at Feb 22, 2014 at 10:47 pm
On Sat, Feb 22, 2014 at 6:39 AM, James Foster wrote:
From what I saw, the plan is to use Go for the Go compiler instead of C in
the 1.3 release.
For Go 1.3, the compilers (both for C and Go) and assemblers of the Go
toolchain will still
be in C.
(e.g. cmd/nm, cmd/pack, cmd/addr2line, cmd/objdump, cmd/?l will all have Go
Go 1.3 might not switch to cmd/link, but let's see. I expect it will take
the place of cmd/?l
(all code generation and assembly tasks have been moved into cmd/?a, cmd/?c
the linker has much less work to do than in previous releases, so replacing
it will cmd/link
seems high probable.)
The transition of Go compiler to Go won't start until after Go 1.3.
Does this open the possibility for a Go debugger instead of GDB?
As others have said. From my observation, the author of ogle (gri) is busy
on the go/types and related packages.
Those packages are is more important than a Go debugger. For example, we
need code refactoring tools and other Go source code handling tool first
currently have gdb to debug Go.
(Disclaimer: the above paragraph about debugger is based on my observation
go-codereviews traffic, gri and others could certainly been developing a Go
without sending CLs.)
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 email@example.com.
For more options, visit https://groups.google.com/groups/opt_out.