[Warzone-dev] buildbot failure in Warzone 2100: Resurrection Project on nightly_mingw32

2009-01-30 Thread buildbot+notifier
The Buildbot has detected a new failure of nightly_mingw32 on Warzone 2100: 
Resurrection Project.
Full details are available at:
 http://build.kynes.de/builders/nightly_mingw32/builds/129

Buildbot URL: http://build.kynes.de/

Buildslave for this Build: i386-debian-etch-2

Build Reason: The web-page 'force build' button was pressed by '': 

Build Source Stamp: 6564
Blamelist: 

BUILD FAILED: failed svn

sincerely,
 -The Buildbot


___
Warzone-dev mailing list
Warzone-dev@gna.org
https://mail.gna.org/listinfo/warzone-dev


[Warzone-dev] buildbot failure in Warzone 2100: Resurrection Project on nightly_mingw32

2009-01-30 Thread buildbot+notifier
The Buildbot has detected a new failure of nightly_mingw32 on Warzone 2100: 
Resurrection Project.
Full details are available at:
 http://build.kynes.de/builders/nightly_mingw32/builds/131

Buildbot URL: http://build.kynes.de/

Buildslave for this Build: i386-debian-etch-2

Build Reason: The web-page 'force build' button was pressed by '': 

Build Source Stamp: HEAD
Blamelist: 

BUILD FAILED: failed compile shell_3

sincerely,
 -The Buildbot


___
Warzone-dev mailing list
Warzone-dev@gna.org
https://mail.gna.org/listinfo/warzone-dev


[Warzone-dev] ping

2009-01-30 Thread bugs buggy
Just checking if list is alive and well.

I haven't heard from many people that use to frequent the list, and
just wondered what everyone was up to?


The MAC people seem to be very quiet, and there has been little mac
related feedback for 2.1, and how the new netcode works between macs 
linux  pc machines.

___
Warzone-dev mailing list
Warzone-dev@gna.org
https://mail.gna.org/listinfo/warzone-dev


Re: [Warzone-dev] assert return macro

2009-01-30 Thread bugs buggy
On 1/29/09, Per Inge Mathisen per.mathi...@gmail.com wrote:
 I want to define a new macro ASSERT_RETURN(expr, retval, ...) that
  asserts in debug builds, and returns with the given return value in
  non-debug builds. This to make it easier to do the right thing when
  coding, which is to first check an entry condition with an assert, and
  then check it again to return on failure. It also has the added
  benefit that it will only evaluate the expression once, unlike
  ASSERT(expr); if (!expr) ... code, since even in non-debug builds we
  evaluate the expression to output logging in case of error.

  An example: ASSERT_RETURN(false, 1, testing);

  This macro will test the expression 'false' and if it fails (always)
  it will assert, if asserts are enabled, and if not (or if continue
  from gdb is used) return 1.

  Since we have had quite a few rounds on the exact definition of the
  ASSERT macro, please have a close look at this patch.


   - Per


This could be very useful.
I was thinking we may do something like a ASSERT_ENTER() as well, to
catch input errors, but that would be much harder to determine a valid
range for some of the input parameters.
(was thinking about the signed/unsigned U/BYTE/WORD/LONG conversions
as well.  We still need to find those suckers)

___
Warzone-dev mailing list
Warzone-dev@gna.org
https://mail.gna.org/listinfo/warzone-dev


Re: [Warzone-dev] 2.2 branch

2009-01-30 Thread bugs buggy
On 1/5/09, Per Inge Mathisen per.mathi...@gmail.com wrote:
 On Sun, Jan 4, 2009 at 10:54 PM, bugs buggy buginato...@gmail.com wrote:
   I was just curious, since the release of 2.1, what is the plan for the
   next version?
   I was thinking that 2.2 should be branched from trunk, and then we
   could pretty much make a release from that ASAP.


 I am pretty much thinking the same thing.


I don't think I have seen responses on this subject from the other members.

Is there anything holding back a 2.2 branch, besides the time factor?

Or should we make a package from current trunk, package the FMVs with
it, and release it for a pre-alpha candidate (without branching) to
see what, if anything needs to be done?
That way, we will get a better idea if we should branch 2.2 now, or
wait a bit longer.

What say you all?

___
Warzone-dev mailing list
Warzone-dev@gna.org
https://mail.gna.org/listinfo/warzone-dev


Re: [Warzone-dev] ping

2009-01-30 Thread Zarel
On Sat, Jan 31, 2009 at 12:37 AM, bugs buggy buginato...@gmail.com wrote:
 Just checking if list is alive and well.

 I haven't heard from many people that use to frequent the list, and
 just wondered what everyone was up to?

 The MAC people seem to be very quiet, and there has been little mac
 related feedback for 2.1, and how the new netcode works between macs 
 linux  pc machines.

I'm here, as you know.

As for the Mac stuff:

I've played quite a few games with me on Mac OS X 10.5 (Intel) and
everyone else on Windows. I haven't hosted a game, but I've joined
games, IP, lobby, they've all worked perfectly.

Well, relatively perfectly. As perfectly as it does on Windows, which
means some sync problems, but still playable.

Also, why do you say MAC? MAC always makes me think of MAC
address; Macintosh computers are generally called Macs.

- Zarel

___
Warzone-dev mailing list
Warzone-dev@gna.org
https://mail.gna.org/listinfo/warzone-dev