STLIB | Sofa Template Library | Machine Learning library

Several things that need to be fixed. When declaring variables, it's good practice to initialise them at the time of decleration. Rather than int a; a = x; And to only declare variables when needed. But this can obviously come down to preference and practice. In C89 variables had to be declared at the top of the scope but I can tell you're not compiling C89. You also didn't need to loop the rand 12 times. Just two calls is enough if you want two seperate ints. Keep in mind rand isn't very good but for practice it's okay. Placing a new line after print statement can make the output neater. countCorrect and countIncorrect were declared but not initialised to 0 then later incremented. This is bad practice because you don't know the initial value of either variable and you wouldn't get an accurate count. I'm assuming you want to only quit when the user enters 4 but keep looping otherwise? Place the switch outside the loop then after the user guesses the product, read the choice from the user and use that value the end of the do while loop.

You need to use WORKDIR as a Dockerfile instruction, instead of using it together with run instruction.

RUN has 2 forms:

• RUN (shell form, the command is run in a shell, which by default is /bin/sh -c on Linux or cmd /S /C on Windows) RUN

• ["executable", "param1", "param2"] (exec form)

WORKDIR

WORKDIR /path/to/workdir The WORKDIR instruction sets the working directory for any RUN, CMD, ENTRYPOINT, COPY and ADD instructions that follow it in the Dockerfile

Answering my questions:

1) Can I use 'android.arch.persistence.room:testing:1.1.1' without kotlin dependencies?

No, because it relies on it. I found usage of kotlin.reflect.KDeclarationContainer class, for example.

2) If 1 question answer is 'No', can I use kotlin dependency only for testing?

Yes, this lib will be available only for testing using

Yes and no.
It seems that the code is written to imply the difference of "one charact" and "many pieces of charact".

Something like:

Char is one, a single struct.
ListOfChar in itself is a pointer to a single Char, but it implies that there are more of it following. With some way of identifying the last one, this allows a function to work on several, with only one parameter. Even without knowing immediatly how many there are.

There is another similar construct, which you do not mention in your question and which is apart from declaration not used in the shown code, CharNode_ptr. If you allow some pure speculation, I'd guess that the "more following" from above, is implemented in the rest of the code as a linked list.
The implication here is slightly different (or just more detailed), it suggests the additional detail that you find the "other" characts via following the link next inside each struct, provided that it is not NULL.
It is likely that the code is written to NOT imply this detail when using the ListOfChar type identifier, e.g. in the API (shown prototypes) for functions.

Something like:

ListofChar means:
"Hey user, do not worry, it is somehow more than one; but you do not need to know how exactly."

CharNode_ptr means:
"Hey programmer, keep in mind that you are dealing with linked lists."

This: