search for: misuse

Is this a misuse of strtok() in OpenSSH-2.1.1p2? readconf.c:process_config_line() calls strtok() to parse config lines. When it finds oProtocol it calls compat.c:proto_spec() which in turns uses strtok(). However on return of proto_spec(), process_config_line() calls strtok() once more to (quoting from the sourc...

I found the following comment in the ChangeLog for the openSUSE nut package: > * Mon Apr 14 14:00:00 2008 schwab at suse.de > > - Work around misuse of libtool. Find attached the diff's that are applied. Is there any merit in this and/or should we be port this back into the trunk/Testing? Best regards, Arjen -------------- next part -------------- A non-text attachment was scrubbed... Name: nut-libtool.diff Type: text/x-patch Size: 1587...

...tp://stats.stackexchange.com/questions/12651/box-jenkins-model-selection/12662#12662 http://www.insead.edu/facultyresearch/research/doc.cfm?did=46900 ----- Tom Reilly www.autobox.com -- View this message in context: http://r.789695.n4.nabble.com/Discussion-on-time-series-analysis-and-the-use-and-misuse-of-Differencing-tp3652268p3652268.html Sent from the R help mailing list archive at Nabble.com.

--------------------------------------------------------------------- Red Hat, Inc. Security Advisory Synopsis: Potential misuse of squid cachemgr.cgi Advisory ID: RHSA-1999:025-01 Issue date: 1999-07-29 Updated on: Keywords: squid cachemgr.cgi connect Cross references: --------------------------------------------------------------------- 1. Topic: cachemgr.cgi, the manager interface to Squid, is installed by default...

On Mon, May 22, 2017 at 03:33:43AM -0700, Joe Perches wrote: > vhost logging uses of vq_err has a few defects and style inconsistencies. > > o pr_debug already uses pr_fmt so its use in vq_err is defective > however no #defines of pr_fmt exist in this code so no actual > defects exist > o vq_err uses need terminating newlines so add the missing ones > o Coalesce formats

Change kernel-doc "/**" comments to common "/*" comments to prevent kernel-doc warnings: gf100.c:1044: warning: This comment starts with '/**', but isn't a kernel-doc comment. Refer Documentation/doc-guide/kernel-doc.rst * Wait until GR goes idle. GR is considered idle if it is disabled by the gf100.c:1044: warning: missing initial short description on line: *

Change kernel-doc "/**" comments to common "/*" comments to prevent kernel-doc warnings: gk20a.c:49: warning: This comment starts with '/**', but isn't a kernel-doc comment. Refer Documentation/doc-guide/kernel-doc.rst * cvb_mv = ((c2 * speedo / s_scale + c1) * speedo / s_scale + c0) gk20a.c:49: warning: missing initial short description on line: * cvb_mv = ((c2

Change kernel-doc "/**" comments to common "/*" comments to prevent kernel-doc warnings: nouveau_ioc32.c:2: warning: Cannot understand * \file mga_ioc32.c on line 2 - I thought it was a doc line nouveau_ioc32.c:52: warning: Function parameter or member 'filp' not described in 'nouveau_compat_ioctl' nouveau_ioc32.c:52: warning: Function parameter or member

Quite a few packages have used this construct to launch a device, but it has several flaws. It's not clear in most cases that a package really needs to launch a new device (R will do so if needed), but 2.7.0 provides a function dev.new() to do so. (If you really need this in a GPL-ed package that must run in R < 2.7.0, consider copying dev.new.) You cannot assume any arguments for

>From the R FAQ Bug reports on contributed packages should be sent first to the package maintainer, and only submitted to the R-bugs repository by package maintainers, mentioning the package in the subject line. and you are NOT the listed maintainer. Do learn to read FAQs before causing unnecessary work for other people (as the R posting guide asks). Please do as the FAQ asks. On

As for skinny metadata, key.offset stores levels rather than extent length. Signed-off-by: Liu Bo <bo.li.liu@oracle.com> --- btrfs-image.c | 4 ++-- 1 file changed, 2 insertions(+), 2 deletions(-) diff --git a/btrfs-image.c b/btrfs-image.c index 739ae35..e5ff795 100644 --- a/btrfs-image.c +++ b/btrfs-image.c @@ -798,9 +798,9 @@ static int copy_from_extent_tree(struct metadump_struct

The code was passing sizeof(char *) - not the length of the buffer - to strlcpy and snprintf. Change the function to take the length of the buffer as a parameter. Fixes the warning: argument to 'sizeof' in 'snprintf' call is the same expression as the destination; did you mean to provide an explicit length? Signed-off-by: Jonathan Boeing <jonathan.n.boeing at gmail.com>

...) {....} inline int B(int x); }; inline int X::B(int x) {...} Per the language standard, A and B are semantically identical, both "inline". It's been suggested that we should omit the inlinehint on A, on the grounds that many C++ programmers do not know this, and therefore misuse the construct. I want to get some other views on this. Do you think it's a good idea? (For those of you who consider yourselves C++ programmers - and not FE language lawyers, who are supposed to know what the standard says - did you know this?)

'Writing R Extensions' tells you that $ needs to be escaped in Rd files outside \code and similar. So I was surprised to find that ca 80 CRAN packages have constructions like (from ISwR) \item{\code{folate}}{ a numeric vector, folate concentration ($\mu$g/l). } This does not render sensibly in non-latex conversions, and it is what we have \eqn{} for. That $ needs to be

Dear all, I wonder if it is "bad style" (or something worse) to create an "update" function which does not work on model objects of the lm, glm etc. type. Specifically, I have some graph objects (graphs as mathematical objects, not as displays) which I want to alter and for that purpose I thought of writing an update function. Would doing so violate a "deeper

...tinkering! I actually ran two sets of studies, and Wayne Seguin kindly provided a lot of guidance and support in getting them running. Thanks Wayne! Also, EngineYard provided the hardware for the test. The first test looked at Mongrels running with nginx fair proxy vs. without it: http://www.misuse.org/science/2008/04/07/thin-ruby-on-rails-nginx-fair-proxy-performance-testing/ The second test looked at Mongrels vs Thin as the application handler for Rails: http://www.misuse.org/science/2008/04/07/thin-vs-mongrel-a-ruby-on-rails-performance-shootout/ Overall the results were not so surpris...

Developers: I hope this is the appropriate place to post this request. I am getting a core dump in an application of sapply. A simplified example is the following. Because simplify=TRUE is the default for sapply and tapply, the following works x <- 1:5; sapply(x,list) but the following dumps core with an access violation x <- 1:5; myf <- function(x) list(x,x); sapply(x,myf)

This code or subtle variations of it appears in multiple targets. It tries to convert from a register to a register class using getRegClass, but getRegClass is really supposed to take a register class enum value and get the register class object for it. It doesn't convert a register to a class. In fact there's not always a single or canonical class for a given register. What is the right

>From this bug report (it's a proposal for speedup only, not a bug), https://bugs.r-project.org/bugzilla/show_bug.cgi?id=16895#c6 the fact that you can construct factors with non-unique aka "duplicated" levels in R has been re-raised. As mentioned there, we had a small discussion here (on 'R-devel') a bit more than 7 years ago, where I had said that indeed R core had

Hi all, I need my rsync to listen on port 8090 as well as on the standard rsync port. Is this possible, and if so, how does one do this? Thanks! Robert -------------- next part -------------- HTML attachment scrubbed and removed