Groups | Search | Server Info | Keyboard shortcuts | Login | Register [http] [https] [nntp] [nntps]


Groups > comp.lang.misc > #1499

Re: should we Go now?

From Ivan Shmakov <oneingray@gmail.com>
Newsgroups comp.lang.misc, comp.lang.perl.misc
Subject Re: should we Go now?
Date 2013-02-25 13:32 +0000
Organization Aioe.org NNTP Server
Message-ID <874nh08qpb.fsf@violet.siamics.net> (permalink)
References <87hal29eeb.fsf@violet.siamics.net> <87ehg5u0r3.fsf@sapphire.mobileactivedefense.com> <874nh1abn5.fsf@violet.siamics.net> <24eqv9-9mq.ln1@anubis.morrow.me.uk>

Cross-posted to 2 groups.

Show all headers | View raw


>>>>> Ben Morrow <ben@morrow.me.uk> writes:
>>>>> Quoth Ivan Shmakov <oneingray@gmail.com>:

 >> Doesn't seem to be all that applicable to Go.  Consider that:

 >> * Perl uses GC;

 > Perl uses refcounting.  One of Perl's flaws is that it doesn't use
 > proper GC.

	I know about the deficiencies of refcounting.  However, it was
	my understanding that it works quite well for Perl in practice.

[...]

 >> * Go has pointers.

 > Real pointers, or Perl-style safe references?  Real pointers are a
 > major disadvantage, in my book, for any language which isn't C.

	Given that Go has no pointer arithmetic, I'd say that these are
	"safe references."

 >> Somehow, Go seem to lack destructors, although I don't quite
 >> understand how this goes well along with having a GC.  But perhaps
 >> it doesn't.

 > True GC and destructors don't play very well together, because
 > objects get destroyed at arbitrary times.  Mechanisms like the
 > 'defer' you mentioned originally are more appropriate for cleaning up
 > non-memory resources.

	I may be using a wrong term, but the GC's I've worked with
	typically allowed for a procedure to be run when an object
	is about to be removed.

	How would, say, Perl's IO handles be possible without the
	availability of a mechanism to properly give the resources back
	to the underlying system when such a handle is to be removed?

-- 
FSF associate member #7257

Back to comp.lang.misc | Previous | NextPrevious in thread | Next in thread | Find similar


Thread

should we Go now? Ivan Shmakov <oneingray@gmail.com> - 2013-02-24 10:47 +0000
  Re: should we Go now? Ben Morrow <ben@morrow.me.uk> - 2013-02-24 13:40 +0000
  Re: should we Go now? Rainer Weikusat <rweikusat@mssgmbh.com> - 2013-02-24 16:37 +0000
    Re: should we Go now? Ivan Shmakov <oneingray@gmail.com> - 2013-02-24 17:02 +0000
      Re: should we Go now? Rainer Weikusat <rweikusat@mssgmbh.com> - 2013-02-24 19:38 +0000
        Re: should we Go now? Nils M Holm <news2009@t3x.org> - 2013-02-25 07:23 +0000
          Re: should we Go now? Rainer Weikusat <rweikusat@mssgmbh.com> - 2013-02-25 17:30 +0000
      Re: should we Go now? Ben Morrow <ben@morrow.me.uk> - 2013-02-24 21:42 +0000
        Re: should we Go now? Rainer Weikusat <rweikusat@mssgmbh.com> - 2013-02-24 22:26 +0000
        Re: should we Go now? Rainer Weikusat <rweikusat@mssgmbh.com> - 2013-02-25 01:04 +0000
        Re: should we Go now? Ivan Shmakov <oneingray@gmail.com> - 2013-02-25 13:32 +0000
          Re: should we Go now? Ben Morrow <ben@morrow.me.uk> - 2013-02-25 15:28 +0000
            Re: should we Go now? Rainer Weikusat <rweikusat@mssgmbh.com> - 2013-02-25 17:54 +0000
      Re: should we Go now? "BartC" <bc@freeuk.com> - 2013-02-25 01:29 +0000
        Re: should we Go now? Ivan Shmakov <oneingray@gmail.com> - 2013-02-25 13:12 +0000
  Re: should we Go now? Ivan Shmakov <oneingray@gmail.com> - 2013-02-24 17:04 +0000
  Re: should we Go now? Bjoern Hoehrmann <bjoern@hoehrmann.de> - 2013-02-24 18:24 +0100
  Re: should we Go now? Keith Thompson <kst-u@mib.org> - 2013-02-25 17:01 -0800

csiph-web