SMC | Read-only wrapper for macOS 's System Management Controller

You can get rid of the warning bit by wrapping it with suppressWarnings() but the first bit of the message looks like just a print statement in the alpha() function. This will work though

I solved this problem thanks to some help from @rossta. I needed to move all my import statement for the splitting.js module from application.js to the script.js file in which the module was being called. So I added the following to the top of scripts.js:

You can't mention users in the author field or the title field, better move it to the description.

You've declared it, which means the compiler is happy to compile it. The declaration is like the name of the function: the compiler knows that the function exists and can compile code that calls it.

But in order to link it, you have to link in the definition (the implementation) of that function. The linker is telling you that it doesn't have the actual implementation of that function that you declared.

Most likely your link line is wrong, almost surely you either forgot to put the library on the link line at all or else you put it in the wrong place, but since you didn't provide us with any information about the link command that was run to generate that error message or the makefile rule you used to link, there's no way we can help.

1. Something might be broken with my Virtual Environments

The easiest solution is using a venv - it's standard library and thus the best baseline for virtual enviorments. (For completness it's worth mentioning that historically there have been a number of solutions for this.) As an example creating a venv with the PyCharm GUI is easy, it creates a new interpreter from the base Python interpreter optionally sharing its site-packages. The GUI lets you interface with PyPI to install aditional packages.

Eventually, it's worth learning to do the same using the command line, see venv — Creation of virtual environments. This boils down to 3 commands

1. Create the venv (since you have Python on your PATH)

   c:\>python -m venv c:\path\to\myenv

2. Activate the venv (this is OS specific, see the documentation)

   /bin/activate

3. After activating use pip to install any libraries you want

   pip install library_name

After having the venv created and activated it's ready to use on the terminal (inside or outside PyCharm), or you can use it with run configurations in PyCharm.

Now, in your case you are also using Anaconda, which manages the packages and the environments for you. But it's important to realize that what Anaconda does for the most part are the above steps wrapped in it's own GUI, see the similarities with Finding your Anaconda Python interpreter path.

Besides this, there's a hard rule that venvs should not be copied or moved. They have hardcoded paths inside them that will break. So, when you create a venv use it in the directory where you created it. The whole point of venvs is that if you break something you simply create a new one on-the-fly. Eventually, you'll want to write your own shell script to automate creating venvs.

1. Something might be broken with my PATH

Your PRINT token can only be matched by the blk_expr rule through this path:

There is no path for retblock_expr to recognize anything that begins with the PRINT token.

As a result, it will not matter which order you have elk_expr or retblock_expr.

There is no parser rule in your grammar that will match a PRINT token followed by a LPR token. a block_expr is matched by the program rule, and it only matches (ignoring wsp) block_expr or retblock_expr. Neither of these have alternatives that begin with an LPR token, so ANTLR can't match that token.

print(...) would normally be matched as a function call expression that accepts 0 or more comma-separated parameters. You have no sure rule/alternative defined. (I'd guess that it should be an alternative on either retblock_expr or block_expr

That's the immediate cause of this error. ANTLR really does not have any rule/alternative that can accept a LPR token in this position.

Both global and a are listed in your grammer under kwr rule.

kwr is mentioned in the inl rule which isn't used anywhere. So your parser don't know how to deal with inl and don't know what to do with two inl chained together (global a)

Bundle Patches are always cumulative. You can install the last one.

Generally you should try to stay up-to-date. it's not just application bugs which are fixed but also security bugs. The closer you stay to the current patch level the more secure you are.