Account Options

  1. Sign in
The old Google Groups will be going away soon, but your browser is incompatible with the new version.
Google Groups Home
« Groups Home
Message from discussion process.nextTick semantics

Received: by 10.216.199.160 with SMTP id x32mr830898wen.10.1338568187567;
        Fri, 01 Jun 2012 09:29:47 -0700 (PDT)
X-BeenThere: nodejs-dev@googlegroups.com
Received: by 10.216.214.136 with SMTP id c8ls2212090wep.8.gmail; Fri, 01 Jun
 2012 09:29:39 -0700 (PDT)
Received: by 10.216.226.31 with SMTP id a31mr830265weq.11.1338568179073;
        Fri, 01 Jun 2012 09:29:39 -0700 (PDT)
Received: by 10.216.226.31 with SMTP id a31mr830264weq.11.1338568179057;
        Fri, 01 Jun 2012 09:29:39 -0700 (PDT)
Return-Path: <jo...@jorgechamorro.com>
Received: from mail-wi0-f176.google.com (mail-wi0-f176.google.com [209.85.212.176])
        by gmr-mx.google.com with ESMTPS id bk8si354848wib.1.2012.06.01.09.29.38
        (version=TLSv1/SSLv3 cipher=OTHER);
        Fri, 01 Jun 2012 09:29:38 -0700 (PDT)
Received-SPF: neutral (google.com: 209.85.212.176 is neither permitted nor denied by best guess record for domain of jo...@jorgechamorro.com) client-ip=209.85.212.176;
Authentication-Results: gmr-mx.google.com; spf=neutral (google.com: 209.85.212.176 is neither permitted nor denied by best guess record for domain of jo...@jorgechamorro.com) smtp.mail=jo...@jorgechamorro.com
Received: by mail-wi0-f176.google.com with SMTP id hn14so589528wib.5
        for <nodejs-dev@googlegroups.com>; Fri, 01 Jun 2012 09:29:38 -0700 (PDT)
        d=google.com; s=20120113;
        h=content-type:mime-version:subject:from:in-reply-to:date
         :content-transfer-encoding:message-id:references:to:x-mailer
         :x-gm-message-state;
        bh=GT+H0HY1FMeHzBCUmHKB21WFzSYnZedhl2PiqTFwGAs=;
        b=mF7E2kfd1kXlGJeDBn5OmsplYZAzQMT8xhY4cwzFXA9/Df/sWQamlqCCjP1aAm9M8+
         1elO/4+RqDYCqp38sLOpIl4icGObN6hww1RtL+0a/MeCHwhRq4BDy0fGvhDsatR8sgGY
         vWnNj+70mlB/YtvHtuSBHJi6BZQ/qu05VdiObaqI0UOQDhxbubwZUM0+A74LsJSTo7y+
         va35jHAM9IeKppC4GZlEOTuaKkfDkuZAwTYPUSvHvHgFX3Wji2+n7+bRj3pgFJU0AZ0J
         v5LVV+EUPH71uH8/JKW40lPdtj1X+IFqbitftj4aG/0Vyp5vgVJ0VTQvgl7KpLwmH8/t
         DMZA==
Received: by 10.216.212.157 with SMTP id y29mr2576045weo.146.1338568178646;
        Fri, 01 Jun 2012 09:29:38 -0700 (PDT)
Return-Path: <jo...@jorgechamorro.com>
Received: from [192.168.0.10] (4.Red-81-44-191.dynamicIP.rima-tde.net. [81.44.191.4])
        by mx.google.com with ESMTPS id j4sm11663641wiz.1.2012.06.01.09.29.36
        (version=TLSv1/SSLv3 cipher=OTHER);
        Fri, 01 Jun 2012 09:29:37 -0700 (PDT)
Content-Type: text/plain; charset=us-ascii
Mime-Version: 1.0 (Apple Message framework v1084)
Subject: Re: [node-dev] Re: process.nextTick semantics
From: Jorge <jo...@jorgechamorro.com>
In-Reply-To: <CAGkHjAWiGwE+=VjfJS8gh7E6UNsEXTsVaOUzfy+xwWQiRuX...@mail.gmail.com>
Date: Fri, 1 Jun 2012 18:29:35 +0200
Content-Transfer-Encoding: quoted-printable
Message-Id: <43E98754-8A4D-44A3-9CBB-F7D2EED1D...@jorgechamorro.com>
References: <CADcwD-E4ii5WK0dyYoALbSdD+JGmXJqpF_ZDQLcO4VFqGxA...@mail.gmail.com> <2d7342d6-d6fd-43af-a1ed-595469f9f...@m3g2000vbl.googlegroups.com> <1e658fb7-139f-4646-83f8-91e07fdc61ba@googlegroups.com> <BBC3E0AC-EE8E-4C05-ACDB-9AF4939B8...@gmail.com> <CADcwD-HBqtXQz45UK8RHB1VXDL_U6y=oZbOi=bSzkdnppJj...@mail.gmail.com> <E75204C1-4AA3-4D35-9612-12FDE7658...@jorgechamorro.com> <CAGkHjAWcZOZuLe=5roczN-9vWup1vyqaAnNAuQJ2cEMC2SM...@mail.gmail.com> <CAGkHjAWiGwE+=VjfJS8gh7E6UNsEXTsVaOUzfy+xwWQiRuX...@mail.gmail.com>
To: nodejs-dev@googlegroups.com
X-Mailer: Apple Mail (2.1084)
X-Gm-Message-State: ALoCoQlUwk4BzlXdHAnBL6hK83cUwe0/MusJLg+s3YkMfO0WuXYaz1wcyEzoiv2XpBUQGApZgyuf

On May 30, 2012, at 12:57 AM, Tim Caswell wrote
>> On Tue, May 29, 2012 at 5:22 PM, Jorge <jo...@jorgechamorro.com> =
wrote:
>>=20
>> FYI: setImmediate =3D=3D=3D nextTick and identical to a =
setTimeout(f,0) without the clamping.
>=20
> so I guess in a way setImmediate(fn) could be described fairly =
accurately as a faster setTimeout(fn, 0).  As I understand timer events =
get put at the end of the queue as well.
>=20
> <snip>

LOL, see "nextTick(f) vs SetTimeout(f, 0)" (it's from ~ 2 years ago =
:-P):

=
<http://groups.google.com/group/nodejs/browse_thread/thread/b564ac42ac53e4=
24/7b85530b465f578d>
--=20
Jorge.