[parrot/parrot] f5265d: try something else, use a static volatile global h...

noreply at github.com noreply at github.com
Sat Nov 12 02:13:05 UTC 2011


  Branch: refs/heads/green_threads_win
  Home:   https://github.com/parrot/parrot

  Commit: f5265dd5af34438dce90130064b01b608a8d6bc4
      https://github.com/parrot/parrot/commit/f5265dd5af34438dce90130064b01b608a8d6bc4
  Author: Whiteknight <wknight8111 at gmail.com>
  Date:   2011-11-10 (Thu, 10 Nov 2011)

  Changed paths:
    M src/platform/win32/alarm.c

  Log Message:
  -----------
  try something else, use a static volatile global handle instead of attaching it to any interp


  Commit: b5bfa41310956ddc0ec99cb10d03029e2003ef73
      https://github.com/parrot/parrot/commit/b5bfa41310956ddc0ec99cb10d03029e2003ef73
  Author: Whiteknight <wknight8111 at gmail.com>
  Date:   2011-11-11 (Fri, 11 Nov 2011)

  Changed paths:
    M src/platform/win32/alarm.c

  Log Message:
  -----------
  Don't use an explicit global timer queue, if we pass NULL we use a process default queue. Implement Parrot_alarm_now. Cleanup


Compare: https://github.com/parrot/parrot/compare/4fce7f8...b5bfa41


More information about the parrot-commits mailing list