Add static method

[LoiNguyenCS]

No description provided.

[LoiNguyenCS]

Professor,

When I was writing the paper for Specimin, I realized that I forgot to handle static method calls in the input program, which is quite embarrassing. This pull request addresses that by adding the necessary code for unsolved static method calls. Additionally, I noticed the existence of the tempDirJDK folder, which I had created a while ago for bug testing purposes. I believe it was accidentally added at some point in the past, so this PR includes the removal of that folder.

In this updated version of Specimin, wildcard imports are no longer allowed. The reason is that we need to distinguish between class and method names in unsolved method calls, such as A.c(). The only reliable way to determine whether A refers to a class or a method is to look at the import statements.

I think the logic of this solution might not apply if there is a method or class instance with the same name as a class among the import statements. But I think the odd is low, since usually people don't name methods or class instances with a capitalized name like they do for classes.

[kelloggm]

Nice catch! Please also add a test for a more complex static call (e.g., one where the programmer uses the fully-qualified name of the class).

[LoiNguyenCS]

Professor,

I've made some changes to the code.

My initial implementation was incorrect. The problem was somewhat concealed because I named my test class Class, coincidentally matching some built-in Java classes. Thus, the program ran without triggering any error.

I've also introduced a more complex method call in the test file.

Please take a look. Thank you.

[LoiNguyenCS]

Professor,

I have updated the codes and the test file.

[LoiNguyenCS]

I don't know why the CI is not running. I think this is a bug of GitHub. But the solutions discussed in that bug report don't seem to be related to our case.

[kelloggm]

I'm still concerned about the string manipulation.

Also, I'm not sure that this code will handle static imports correctly. Can you also add a test that statically imports a method and make sure that the code handles it properly?

[LoiNguyenCS]

Professor,

I'm still concerned about the string manipulation.

I have renamed the related methods and added clarification in the Javadoc to make sure that the expected input will be passed to this string manipulation call.

Also, I'm not sure that this code will handle static imports correctly. Can you also add a test that statically imports a method and make sure that the code handles it properly?

Unfortunately, I wasn't aware of this Java feature until today. Updating Specimin for static imports might involve extensive modifications, such as changing how it reads import statements and updates classAndPackageMap. I suggest addressing this in a separate PR, ideally after resolving issue #41.
`

[kelloggm]

Updating Specimin for static imports might involve extensive modifications, such as changing how it reads import statements and updates classAndPackageMap. I suggest addressing this in a separate PR, ideally after resolving issue #41.

They are rare, so that's fine. Please open an issue for this so we don't forget.

[kelloggm]

When the requested changes are implemented, you can merge without requiring another review from me.