Searched refs:serious (Results 1 – 25 of 63) sorted by relevance
123
| /mirbsd/src/usr.bin/oldroff/refer/ |
| D | TEST | 7 For serious programmers, there are several
|
| D | TEST.out | 7 For serious programmers, there are several
|
| /mirbsd/src/gnu/usr.bin/perl/lib/Memoize/ |
| D | README | 66 TIE presented serious problems. First, it had a bizarre syntax. But
|
| /mirbsd/src/sbin/routed/ |
| D | main.c | 590 int serious) /* 1=failure to bind is serious */ in get_rip_sock() argument
608 if (serious) in get_rip_sock()
|
| /mirbsd/src/gnu/usr.bin/perl/Porting/ |
| D | Contract | 49 preferred unless there is a serious problem with it. Any changes not
69 whole so as to cause serious problems for Perl, the pumpkin holder may
|
| D | pumpkin.pod | 874 More serious is the case where some brilliant person decided to
1162 but not so much that it posed any serious problems.
|
| /mirbsd/src/usr.bin/vi/catalog/ |
| D | README | 49 Otherwise, there is some serious magic going on in common/msg.c to make
153 Duplicate message numbers are a serious problem and have to be fixed.
|
| /mirbsd/src/gnu/usr.bin/lynx/src/chrtrans/ |
| D | README.tables | 6 a cleanup and update would be needed for serious use.
|
| /mirbsd/src/gnu/usr.bin/cvs/ |
| D | BUGS | 9 difference, at least in theory, is that those bugs are less serious.
|
| D | NEWS | 107 potentially serious but which may not be exploitable, assigned CAN-2005-0753
456 presenting a serious security risk. This addresses CVE issue CAN-2004-1080.
936 * A serious error that allowed read-only users to tag files has been
1066 serious data loss. Because of this (and also the fact that it doesn't
|
| /mirbsd/src/gnu/usr.bin/perl/pod/ |
| D | perlfaq1.pod | 88 Versions prior to perl5.004 had serious security problems with
184 "We're really serious about reinventing everything that needs reinventing."
326 like "non serious" or "not real programming". Consequently, some Perl
|
| D | perl584delta.pod | 216 C<perl -i> could C<fchmod(stdin)> by mistake. This is serious if stdin is
|
| D | perlfaq2.pod | 260 If you're not an accidental programmer, but a more serious and
466 Or maybe they need very serious hand-holding and contractual obligations.
|
| D | perl581delta.pod | 952 is not serious and can be ignored.
964 This is not that serious, though, since the native malloc works just
|
| D | perl570delta.pod | 22 a serious compromise instead of reporting the exploit attempt. If you
|
| D | perlobj.pod | 493 A more serious concern is that unreachable memory with a non-zero
|
| D | perlfaq9.pod | 78 die "But this one is serious";
|
| /mirbsd/src/usr.bin/vi/docs/ |
| D | TODO | 4 COMMON: There's a serious problem with error returns -- we need to separate
|
| /mirbsd/src/gnu/usr.bin/perl/ext/Data/Dumper/ |
| D | Changes | 82 Bugfix that was serious enough for new release--the bug cripples
|
| /mirbsd/src/gnu/usr.bin/perl/lib/Text/Balanced/ |
| D | Changes | 43 - fixed serious bug with embedded division operators ("/")
|
| /mirbsd/src/lib/libncurses/src/doc/ |
| D | hackguide.doc | 233 serious need to run this, you probably belong on our development team!
282 These files have serious hooks into the tty driver and signal
352 terminfo files. If System V or XPG4 ever gets serious about using it
|
| /mirbsd/src/gnu/usr.bin/perl/ |
| D | README.mint | 142 far right to the decimal point... Two failures seem to be serious:
|
| /mirbsd/src/gnu/usr.bin/perl/ext/B/ |
| D | README | 293 The following render the compiler useless (without serious hacking):
|
| /mirbsd/src/etc/ |
| D | pf.os | 379 # without some very serious research. Until then, there's an insane
|
| /mirbsd/src/gnu/usr.bin/binutils/gdb/doc/ |
| D | annotate.texinfo | 174 simultaneously, a serious performance problem occurs when the client
|
123