Search results

1) I see "read" status of messages did not migrate. This is ultraminor issue, especially if it was not supposed to migrate. 2) Are there color schemes? I liked the blue&gold. Now I need a few seconds to realize which site I am looking at >_>

Considering how long the place can care for them even when I don't log in at all, I expect that when I ascend they all grow up, become adventurers, and get beaten up by monsters.

If you are changing a .js file, you need to take into account browser caching. And, iirc, javascript files are cached way more aggressively than everything else, to the point that even clearing cache (often?) doesn't remove them from the cache. This is why those files are versioned by changing...

You can wrap the call in another function whose entire purpose is to return a value that will be captured. That does (or at least should, according to my understanding) the same thing AND you can give it a silly name.

Many years ago, I ran my own profiling and found this too (except it was close to 90% of all runtime; maybe it was ADventureResult.compareTo too). So I went and changed things a bit around so that the next profiling looked much better. Then I realized that my "performance" problems were not CPU...

I *think* you can have multiple main functions (with different signatures) And then call them likde script # no argument - main() script bla bla bla # one argument main(string) or main(int) or ... script (bla, bla, bla) # three arguments main(string,string,string) or ....; note the space between...

I did NOT get the same error with jdk_1.8.0_131 either, FWIW (on windows). (and then I waited several hours to post this, oops) (but at least it got me to upgrade to jdk 14 and corresponding eclipse, so *something* good happened from it?)

Well ... yours seems to be doing much larger range than expected ...

IIRC it's because new Integer(int) always creates a new object. You are supposed to use Integer.valueOf(int) instead, it will use cached objects for some predetermined range of small ints (-128..127 or something, but any implementation can change this). This can be important for performance (you...

So apparently, it goes through declared types of variables to check what operations are allowed in the first place, but the actual implementations depend on actual types of values. And there's a special case for string + in Parser.parseExpression that overrides this when the apparent types of...

It makes exactly the sense I already made out of it. If you say new anything(2, 2) then the values you are storing are integers. The declared types are irrelevant. When you do record a_record_containing_only_a_string_field { string str; } record_name = new...

Nope, because that's not how Value [1] is stored internally. You have (effectively) a pointer at an int, or a pointer at a float, and those are always allocated correctly. It's literally impossible in java to access a value [2] as a wrong type. (you can try assigning incompatible object value...

Can you print_html('<tt>fixedwidth here</tt>');?

That one will definitely need some work (assuming it is needed). PID changes on restart.

IIRC, most notably, cron jobs don't have your normal environment variables. Try dumping the output of "set" and comparing to see if there's anything relevant to svn, ssh, certificate configuration, paths to tools (maybe it's running a different version of something)?

It's actually supposed to match as *many* characters as possible while the rest of the pattern still matches (which is why putting multiple .* in a pattern can lead to unbelievably exponentially worse performance). .*? matches "as few as possible", but it has exactly the same backtracking...

Maybe easyfax is stuck somewhere again? ETA: Prisoners of 1337 Leader: Easyfax, FaxBot Replacement (Disabled) (Level 3)

Works for me now.

My batfellow installation is from svn://svn.code.sf.net/p/ccascend/code/batfellow (ETA: and I have the same problem, which is a problem because I have dozens of magazines to go through and each takes many minutes of real time)

IIRC this just happens randomly, in vanilla kol, because those text replacemet effects act randomly and indiscriminately on page html.