Still written by things yourself

zhaozj2021-02-16  57

Recently I don't know if you have a website that is on the MS's website, there is a POST of ten must be used in the VS page. Several tools introduced in this post are indeed very useful, such as Reflector, NUnit, Regulator, and more. It's really clever, the reflector introduced in this is recently checked out a bug, this bug is in viewing the _SIPWnProc function in Microsoft.Windowsce.Forms.dll, the translated C # code is: Internal PAL_ERROR _SIPWnProc (INTPTR HWNTHIS , WM WM, INT WPARAM, INT LPARAM) {if (this.enabledchanged == null) {Return Pal_Error.Handled;} this.enabledchanged.invoke (null, eventargs.empty);} There may be no return value, this bug The version appeared in version 4.0.7.0. After the feedback Email is issued, the author is in contact with me, saying that the latest version 4.0.7.0 has no problem. I don't know if I use it is 4.0.7.0, and Say Sorry. Then I immediately found this problem, I immediately sent him a letter, and later didn't have a version of 4.0.8.0. In fact, it is sometimes safe to use ILDASM to rest assured, at least there will be many logic errors. (I also tried to use the REFLEctor to see the Terrarium program crashed, seeing an Import DLL function, nor did it know if there is a correction.) Another regulator makes me feel more secure. Although this thing seems to be quite good, I actually think he does not have the cumbersome and repeatability of the expression of regular expressions. And let me feel more surprised is that my work is very good, it is wrong, I don't know why. This regular expression is the first phase of the first phase of the .NET CF program source code level optimizer provided, mainly to remove the annotations in the code, string, etc. may cause a part of the wrong understanding.

This expression is as follows: (?> / (?> / (?: [^ / N]) * | / * (?> / * (?! [^ /]) | [^ *]) * / * /) | (? = [@ "" ']) (?> @ (?> / s | / (?> / (:: [^ / n]) * | / * (?> / * (?! [^ / ]) | [^ *]) * / * /)) * "" "" "" | "" ""]) * "|" "(?> //. | [^" "]) * "" "(?> //.) | (? (?: (?> //. | [^ @" "'/ #] | /(?! [* /])) ) | (?> (? #ENDIF (?> / S) * // (?> / S) * NACC | #IF (?> / S) ACC (? > / s) (?> / (?> / (?: [^ / n]) * | / * (?> / * (?! [^ /]) | [^ *]) * / * /) | (? = [@ "" ']) (?> @ (?> / s | / (?> / (:: [^ / n]) * | / * (?> / * (?! [^ / ]) | [^ *]) * / * /)) * "" "" "" | "" ""]) * "|" "(?> //. | [^" "]) * "" "" (?> //. | [^ #] | # (?! Else (?> / s) * // nacc)) # else (?> / S) * / / (?> / s) * NACC) | (? #)))))) ... very exaggerated? I don't know how to design this level if I use regulator to design it, anyway, I use another technology to do, this technology and the software I have used next time. You can try it, what kind of situation will this express in Regulator? The input can be any CatChable group, and the contents inside the Catchable group are spelled out of the annotation and string content (also removed the content between #IF ACC to #ELSE // NACC). However, in Regulator, it is wrong, and the error message says ")" This symbol is insufficient, I don't know if this problem is wrong, it is still a problem. Regarding this problem, I also gave the regular's support, gave a feedback, I don't know if there is a correction in the latest version? I am using version 2.0.3.0 version. (Most let me feel funny, the reference to the test referous is the version of the .NET CF, not the version of the .NET Framework. It is 1.0.5000, 1.0.3333, it is fun, I don't know if it is. He found that more .Net Cf is more?) Write here, I feel that the regular expression constructor is more assured with the software I wrote, and it is more relaxed to construct more complicated content. The above is still not the longest, and the regular expression used in the second step in the accelerator has 783 characters (with 516 characters above). Like such a complicated thing, if you want to create such a tool such as Regulator (note that it is created, not someone pointing to you), it is really an unimaginable thing.

转载请注明原文地址:https://www.9cbs.com/read-19201.html

New Post(0)