Как стать автором
Обновить

Комментарии 3

Где-нибудь ещё в манах вы видели фразу «probably shouldn't»?

Конечно видели :)
$ find /usr/share/man -type f -name '*.gz' -exec sh -c 'gzip -dc {} | grep -C3 "probably shouldn"' \;
There is one exception. If you use an alphanumeric character as the
delimiter of your pattern (which you probably shouldn't do for readability
reasons), you have to escape the delimiter if you want to match
it. Perl won't warn then. See also \*(L"Gory details of parsing
quoted constructs\*(R" in perlop.
...
You probably shouldn't rely upon the \f(CW\*(C`warn()\*(C'\fR being podded out forever.
Not all pod translators are well-behaved in this regard, and perhaps
the compiler will become pickier.
...
Please, unless you're hacking the internals, or debugging weirdness, don't
think about the \s-1UTF8\s0 flag at all. That means that you very probably shouldn't
use \f(CW\*(C`is_utf8\*(C'\fR, \f(CW\*(C`_utf8_on\*(C'\fR or \f(CW\*(C`_utf8_off\*(C'\fR at all.
...
You probably shouldn't use these functions.
...
These functions expose internal values from the \s-1TLS\s0 handshake, for
use in low-level protocols.  You probably should not use them, unless
entropy pool is considered to be initialized.
...
Unless you are doing long-term key generation (and most likely not even
then), you probably shouldn't be reading from the
.IR /dev/random
...
is not intended for use in applications or interactive sessions\&. Its purpose is to allow an external transaction manager to perform atomic global transactions across multiple databases or other transactional resources\&. Unless you\*(Aqre writing a transaction manager, you probably shouldn\*(Aqt be using

Зачем это может быть нужно на практике, я пояснять не буду :-)

Я так понимаю что бы защитить от отладки свою программу?
скорее не от отладки, а от реверс инжиниринга.
Зарегистрируйтесь на Хабре , чтобы оставить комментарий

Публикации

Истории