search for: baz

Hi all, I expect I'm getting something wrong, but cat("foo bar baz foo bar baz foo bar baz", fill = 10) should be broken into lines of width 10, whereas I get: > cat("foo bar baz foo bar baz foo bar baz", fill = 10) foo bar baz foo bar baz foo bar baz This is on R 3.4.3, but I don't see mentions of it fixed in 3.4.4 or r-devel NEWS. Chee...

...> const T& as() const { return dynamic_cast<const T&>(*this); } }; template <typename T> struct API derived: base {}; struct payload {}; // *not* flagged as "default visibility". API void bar(const base& b); API void baz(const base& b); Then I have two different compilation units that provide a similar service, which I can approximate as twice the same feature: down-casting from `base` to `derive<payload>`: // bar.cc #include "foo.hh" void bar(const base& b) { b.as<der...

How can I do this?: foo { name: $bar => "frob" } define foo( $bar = false, $baz = false ) { if #$bar and $baz both defined $cmd = "frobnicate --bar=$bar --baz=$baz ${name}" else if #$bar defined $cmd = "frobnicate --bar=$bar ${name}" else if #$baz defined $cmd = "frobnicate --baz=$baz ${name}" else...

...e a situation where I want to delete some of my excluded patterns but still want to preserve some other. For example consider below source and destination directory hierarchy. Source Dest ---------- --------- /foo/bar/ /foo/bar/ | -> baz | -> baz | -> xyz | -> xyz | -> abc | -> abc | -> old-baz I am below comand using --delete-excluded and as a result rsync deletes exluded directories "baz" and "abc" a...

Howdy, [Please preserve the CC to 424919-forwarded at bugs.debian.org on any replies.] The following bug in Markdown was reported to the Debian bug tracking system. In short, running both the released version of Markdown and the latest beta on * foo > bar > baz produces invalid HTML. ----- Forwarded message from Joey Hess <joeyh at debian.org> ----- From: Joey Hess <joeyh at debian.org> To: Debian Bug Tracking System <submit at bugs.debian.org> Subject: Bug#424919: generates invalid html for a list element immediately followed by a qu...

Suppose I have a string of objects names: name <- c("foo", "bar", "baz") and I would like to use a for loop to automatically create three objects called "foo", "bar" and "baz" accordingly. Then how can this be done" (so that in the workspace, foo = 1, bar = 2 and baz=3) for (i in name) { ..... } Thanks! Mark

...39;' '\''`' + '[' -d from ']' + mkdir from + cd from + for c in '`echo $p | tr '\''/'\'' '\'' '\''`' + '[' -d foo ']' + mkdir foo + cd foo + makepath /tmp/rsync-2.6.6/testtmp.itemize/from/bar/baz + echo ' makepath /tmp/rsync-2.6.6/testtmp.itemize/from/bar/baz' makepath /tmp/rsync-2.6.6/testtmp.itemize/from/bar/baz + p=/tmp/rsync-2.6.6/testtmp.itemize/from/bar/baz + echo /tmp/rsync-2.6.6/testtmp.itemize/from/bar/baz + grep '^/' + cd / ++ echo /tmp/rsync-2.6.6/t...

Hi John, there?s a bug in Markdown.pl: [foo*bar](#) [baz*quux](#) This expands to the following: <p><a href="#">foo<em>bar</a> <a href="#">baz</em>quux</a></p> Those `*` should either be disregarded or the tags should nest correctly: 1. <p><a href="#">foo...

...func ~bar:v But as a special case, if the variable is called bar already, then this works: let bar = "hello" in func ~bar because ~bar is short for ~bar:bar (and the same for optional parameters like ?foo). This leads naturally to code that looks like: let other_func ~foo ~bar ?baz = func ~foo ~bar ?baz Issue 2: Optional arguments are implemented as option types (eg. None, Some foo), except when defaults are used If a function is defined as: let func ?foo ~bar () = ... then bar is passed as an ordinary parameter, it's just that at compile time it i...

Hi, I find it would be very convenient to nest resources in two levels, so a member is only sensible as a part of a club, and a fee pament is only sensible in the context of a club and a member. Is it possible to nest nested resources? How would the syntax be? I have tried just nesting the assignment in routes.rb, but failed to get it right What do ou think? Is it possible? /Fredrik --

...: None Group: None Status: Open Resolution: None Priority: 3 Submitted By: Erik Hetzner (egh) Assigned to: Nobody (None) Summary: Block''s return value is dropped on stubbed yielding methods. Initial Comment: Best explained with an example: test: foo = mock() bar = mock().stubs(:get_baz).returns(:baz) foo.stubs(:with_something).yields(bar) real code: baz = foo.with_something do |bar| bar.get_baz.to_s end baz should now be "baz", but is nil because we have not specified a return value for the stub. Now, we could set add .returns("baz"), but that me...

Hi, I read below lines in rsync v3.0.5 for --relative option. if you used this command: rsync -av /foo/bar/baz.c remote:/tmp/ ... this would create a file named baz.c in /tmp/ on the remote machine. If instead you used rsync -avR /foo/bar/baz.c remote:/tmp/ then a file named /tmp/foo/bar/baz.c would be created on the remote machine, preserving its full path It is also possible to limit the amount of path i...

...For example: select * from foo where bar < 10 ; is similar to foo[foo["bar"] < 10,] I'm just wondering how many other SQL-like manipulations can be done on a data frame? As an extreme example, is it reasonable to assume there is an R equivalent to: select bar, bat, baz, baz*100 as 'pctbaz' from foo where bar like %xyz % order by bat, baz desc ; Regards, - Robert http://www.cwelug.org/downloads Help others get OpenSource software. Distribute FLOSS for Windows, Linux, *BSD, and MacOS X with BitTorrent

...c-3.0.0 /scratch/bfriesen/build/rsync-3.0.0/testtmp /scratch/bfriesen/build/rsync-3.0.0/testtmp/itemize /scratch/bfriesen/build/rsync-3.0.0/testtmp/itemize/from /scratch/bfriesen/build/rsync-3.0.0/testtmp/itemize/from/foo makepath /scratch/bfriesen/build/rsync-3.0.0/testtmp/itemize/from/bar/baz /scratch /scratch/bfriesen /scratch/bfriesen/build /scratch/bfriesen/build/rsync-3.0.0 /scratch/bfriesen/build/rsync-3.0.0/testtmp /scratch/bfriesen/build/rsync-3.0.0/testtmp/itemize /scratch/bfriesen/build/rsync-3.0.0/testtmp/itemize/from /scratch/bfriesen/build/rsync-3.0.0/testtmp/itemize/from/ba...

...e following gives a slightly different error, but I assume it has a similar origin: bar <- function() 1 foo <- function(bar) { if (missing(bar)) bar <- bar() bar } foo() This version works fine though (so the rule probably involves function arguments somehow): foo <- function(baz) { if (missing(baz)) { baz <- function() 2 baz <- baz() } baz } foo() -Deepayan

Is it possible for a pass to get access to the command line options passed to it? That is, if I use the CommandLine library to define cl::opt<int> Foo("foo", ...); cl::opt<int> Bar("bar", ...); cl::opt<bool> Baz("baz", ...); and the user runs "opt -load mypass.so -foo=123 -std-compile-opts -baz", can I somehow get a string containing "-foo=123 -baz"? I suppose as a last resort I can process /proc/self/cmdline, but if there's a cleaner approach, I'd prefer that. Than...

...999 i686 unknown and am wondering whether it's a fundamental shortcoming of the SSH protocol that argument splitting is not preserved from client to server, but instead the argument list is re-split on whitespace. E.g., from my machine `gellar', I execute: % ssh gellar args foo bar 'baz bong' ARG0 = /usr/home/gregb/bin/share/args, NumArgs = 4 1 = "foo" 2 = "bar" 3 = "baz" 4 = "bong" (where args is just a script that outputs the arguments), instead of what I get when I run args directly: % args foo bar 'baz bong' ARG0 = /...

...with deopt bundles itself. Our notion of of "deopt bundles are readonly" is broken to begin with, and that is what's manifesting as the complication we're seeing here. Consider something like ``` declare @foo() readonly def @bar() { call @foo() [ "deopt"(XXX) ] } def @baz() { call @bar() [ "deopt"(YYY) ] } ``` Right now according to the semantics of "deopt" operand bundles as in the LangRef, every call site above is readonly. However, it is possible for @baz() to write to memory if @bar is deoptimized at the call site with the call to @foo. Yo...

...v, I'm glad to hear llvm-objdump is getting attention. I'm unclear on how much output specialization one could (or should) do for ELF vs. Mach-O. If you're game, let's compare an example: $ cat labeltest.s .text foo: nop bar: bum: nop jmp bar jmp bum jmp baz nop baz: nop Assembling for x86 and llvm-objdump'ing, i get $ llvm-mc -arch=x86 -filetype=obj labeltest.s -o x86_labeltest.o $ llvm-objdump -d x86_labeltest.o x86_labeltest.o: file format ELF32-i386 Disassembly of section .text: foo: 0: 90...

....diff,patches/slp.diff fails (most of the time) in the itemize test: ----- itemize log follows Testing for symlinks using 'test -h' makepath /usr/src/packages/BUILD/rsync-3.0.2/testtmp/itemize/from/foo makepath /usr/src/packages/BUILD/rsync-3.0.2/testtmp/itemize/from/bar/baz cd+++++++++ ./ cd+++++++++ bar/ cd+++++++++ bar/baz/ >f+++++++++ bar/baz/rsync cd+++++++++ foo/ >f+++++++++ foo/config1 >f+++++++++ foo/config2 >f+++++++++ foo/extra cL+++++++++ foo/sym -> ../bar/baz/rsync >f..T...... bar/baz/rsync >f..T...... foo/config1 >f.sTp..... foo/con...