//шифруем блок
if (1 != EVP_EncryptUpdate(ctx, out_buffer, &len, buffer, BUFF_SIZE))
handleErrors();
printf("substr encr is %s\n", (char *)out_buffer);
//запоминаем результат
e_param->result.append((char *) out_buffer);
index++;
e_param->data_len -= BUFF_SIZE;
An operator function shall either be a non-static member function or be a non-member function and have at
least one parameter whose type is a class, a reference to a class, an enumeration, or a reference to an enu-
meration. It is not possible to change the precedence, grouping, or number of operands of operators. The
meaning of the operators =, (unary) &, and , (comma), predefined for each type, can be changed for spe-
cific class and enumeration types by defining operator functions that implement these operators. Operator
functions are inherited in the same manner as other base class functions
std::_Fwd_list_const_iterator<T> cur
e_param.text = (unsigned char *) data->c_str();
...
e_param->text[e_param->data_len] = '\0';
if (1 != EVP_EncryptUpdate(ctx, e_param->result, &len, e_param->text, e_param->data_len))
К примеру, если в символьном типе цифра, как мне узнать, что там цифра или буква?
git rebase --onto <куда> <начало ветки> <конец ветки>
First let’s assume your topic is based on branch next.
For example, a feature developed in topic depends on some functionality
which is found in next.
o---o---o---o---o master
\
o---o---o---o---o next
\
o---o---o topic
We want to make topic forked from branch master;
for example, because the functionality on which topic depends
was merged into the more stable master branch.
We want our tree to look like this:
o---o---o---o---o master
| \
| o'--o'--o' topic
\
o---o---o---o---o next
We can get this using the following command:
git rebase --onto master next topic