docstore | A basic site for hosting static documents

If you declare strings like

Your input probably has trailing white space which (.*) is picking. ([^[:space:]]*) seems to work.

The values of match variables do indeed stay around until the next successful pattern match (or until the scope in which the match occurred is exited).

In your case, they changed because there was a successful pattern match. You successfully matched against the pattern , . The capture variables will therefore reflect the text captured by the captures of that match. $1 returns the text matched by the non-existent first capture, so it returned undef.

If I try this schema:

Sadly it comes down to you can't do anything about it.

As per .net's DLL handling DLL's cannot be unloaded individually without closing the application domain. And while Unity picks up the changes done to the DLL the old version is kept in memory and used at runtime in the editor. A "funny" thing you can do to see this in action is by deleting the native plugin from within the editor. Confirm that you want to delete the file. The file will dissapear from the inspector. However if you right click the folder and refresh (ctrl+r) you will see that the file gets reconstructed (this also happens when hitting "re-import all", as the application domain isn't closed, despite unity restarting).

When building the application it will however use the locally stored file, and not the memory stored file. Hence the plugin being updated on the build.

There is no way to unload an individual assembly without unloading all of the application domains that contain it. Even if the assembly goes out of scope, the actual assembly file will remain loaded until all application domains that contain it are unloaded.

source

This has been a problem for some time now, and people have made attempts for work arounds and/or fixes, but as far as I am aware the "work arounds" that exist now are for windows only. here are some links to discussions about it.

• "Unload a plugin"
• "Reloading native plugins"

I suppose something that could be done is writing a wrapper that automatically restarts Unity when the dll has been edited... Although this won't solve the issue it'll atleast make it somewhat less of a hassle.

The reason of this is the 4MB per-value limit for string attributes (http://sphinxsearch.com/docs/devel.html#conf-sql-attr-string). The reason you see 0.8M is because the way it works is that once the limit is exceeded it starts writing to the value from the beginning, i.e. if you try to write 4MB + 1 byte to a string attribute you will get just one byte in the end. The provided INSERT command is 4.8M, that's why you get the value of about 0.8M size.

Thanks for pointing this out. We'll improve this behavior in Manticore Search.

Hmm, I just tried copy/pasting your test_index to a config file, and starting a sphinx3 instance...