What's up with BOS?

[Argh]

Eh, the code's been that way forever, and it appears to work. Like I said, the game-logic's working.

Anyhow, I hear you on your first point, but even if that suddenly fixed stuff... well, I'd be right back to "suppress the errors or rewrite everything", which isn't much of a choice atm.

[AF]

How do you know those are your only two outcomes of the experiment? If it works, then you have been armed with valuable information as to what the problem is that can be used to help fix the BOS problem. It may reveal that the problem is a trivial simple one that can be changed in 5 minutes but did not occur to anybody.

Or, it may reveal that there is a good abstraction that would save you immense amounts of time in conversion to lua.

Or it may reveal an opportunity that was not available before using bos, thus justifying the expense of conversion.

Put simply, you do not know yet, and it is unwise to base judgements on speculations.

[FLOZi]

Also,

Is this:

Code: Select all

-- snip

Not more convoluted, error prone, and unreadable, than this? :

Code: Select all

-- snip

That and renaming DelayedCall(fun) to DelayCall(call)

ipairs and table.insert are slower than the method Argh has used, according to profiling by jk.

[Argh]

Er... yeah, but nevermind that stuff, it's irrelevant.

Anyhow, I'll be able to spend a bit more time testing a few more things (I did a full removal of all the P.U.R.E. core Gadgets- nothing, so I need to do World Builder and LUPS before deciding what I'll do, short of someobody on Dev telling me that "oh, we changed X, it is why your stuff is broke") some time tomorrow evening.

[Argh]

Thus far, a big fat zero.

6 hours or thereabouts looking for a phantom "error" that doesn't stop gamecode from running correctly, and there's nothing pointing towards the issue, all of which (by definition) involves something that worked correctly 6 months ago

Oh well, I guess I'll just suppress it and move on.