Re: [Rails-devel] ORs per SR

[Brett L. <wak...@ea...>]

I'm testing it out, and it seems to work ok.

2 bugs I'm finding in my testing:

1. Portfolio.removeTrain() can sometimes throw a NullPointerException
  It happened to me when a company had to drop a train when 5-trains came out.
  I think this was the second time this company had to drop trains, because earlier on, I had to drop a train when 4-trains were bought.

This looks like we just need to check the element in the list to make sure it's not null, and if it is null, find the next train in the list that has the same parameters as the train selected for removal.

2. The purchase of the first 5-train doesn't immediately close all Private companies.


---Brett.


-----Original Message-----
>From: Erik Vos <eri...@hc...>
>Sent: Jan 3, 2006 6:24 PM
>To: rai...@li...
>Subject: [Rails-devel] ORs per SR
>
>The number of ORs per SR was sort of implemented,
>but hardcoded for 1830, and with a bug that reduced
>the number of ORs by 1 if it was >1.
>
>It should now work correctly.
>
>Erik.
>
>
>
>
>-------------------------------------------------------
>This SF.net email is sponsored by: Splunk Inc. Do you grep through log files
>for problems?  Stop!  Download the new AJAX search engine that makes
>searching your log files as easy as surfing the  web.  DOWNLOAD SPLUNK!
>http://ads.osdn.com/?ad_id=7637&alloc_id=16865&op=click
>_______________________________________________
>Rails-devel mailing list
>Rai...@li...
>https://lists.sourceforge.net/lists/listinfo/rails-devel