Displaying 20 results from an estimated 124 matches for "pushbacks".
Did you mean:
pushback
2002 Dec 27
0
parse and pushBack (PR#2396)
Is this the last bug of the year? Well, it's the last one from me, anyway...
The "parse" function seems to give erratic behaviour when used in
conjunction with "pushBack" on an open connection (R1.6.1, Windows 2000).
Try this:
> { cat( c( '1', 'a+b', '2'), file='r123.r', sep='\n');
tcon_ file( 'r123.r'); open( tcon);
2003 Nov 05
1
read.table leaves out data when reading multiple-line records (PR#4955)
Dear all,
I discovered that read.table (RW1.8.0) leaves out data when reading
multiple-line records.
Replication code at the end
Best regards
Jens Oehlschlägel
> filename <- "c:/tmp/c2.csv"
>
> data <- data.frame(a=c("c", "e\nnewline"), b=c("d", '"quoted
simpleline"'))
>
> #look at the data
>
2009 Sep 12
3
[LLVMdev] [proposal] Extensible IR metadata
Dan Gohman wrote:
> On Sep 11, 2009, at 9:57 AM, Chris Lattner wrote:
>
>
>> Devang's work on debug info prompted this, thoughts welcome:
>> http://nondot.org/sabre/LLVMNotes/ExtensibleMetadata.txt
>
> The document mentions "instructions" a lot. We'll want to be able to
> apply metadata to ConstantExprs as well at least, if not also Arguments
>
2008 Jun 11
1
read.table() causes segfault with incorrect data (PR#11627)
Full_Name: Juho Vuori
Version: 2.7.0 (2008-04-22)
OS: Linux poseidon.fimr.fi 2.6.23.17-88.fc7PAE #1 SMP Thu May 15 00:22:53 EDT 2008 i686 i686 i386 GNU/Linux
Submission from: (NULL) (193.166.188.194)
Calling read.table() twice the following way causes a segmentation fault in R.
Run R and type the following commands:
> read.table(stdin())
0: 1 2 3
1: 3
2:
Error in scan(file, what, nmax, sep,
2009 Sep 12
0
[LLVMdev] [proposal] Extensible IR metadata
On Sep 11, 2009, at 7:17 PM, Nick Lewycky wrote:
> Dan Gohman wrote:
>> On Sep 11, 2009, at 9:57 AM, Chris Lattner wrote:
>>> Devang's work on debug info prompted this, thoughts welcome:
>>> http://nondot.org/sabre/LLVMNotes/ExtensibleMetadata.txt
>> The document mentions "instructions" a lot. We'll want to be able to
>> apply metadata to
2009 Sep 12
1
[LLVMdev] [proposal] Extensible IR metadata
Chris Lattner wrote:
>
> On Sep 11, 2009, at 7:17 PM, Nick Lewycky wrote:
>
>> Dan Gohman wrote:
>>> On Sep 11, 2009, at 9:57 AM, Chris Lattner wrote:
>>>> Devang's work on debug info prompted this, thoughts welcome:
>>>> http://nondot.org/sabre/LLVMNotes/ExtensibleMetadata.txt
>>> The document mentions "instructions" a lot.
2015 Apr 02
1
Next stable release?
Hello,
Are there any chances of next stable release appearing soonish? I'm
getting pushback from Homebrew maintainers about the massive amount of
patching required to build the current stable on Mac, since all the
patches have been merged in after last stable.
(I'm also getting pushback about the 4GB download of virtual
appliance, but as I understand that one is non-optional. Don't
2018 May 29
1
Buffering in R 3.5 connections causes incorrect data in readChar
Tomas,
Thank you for the explanation. I see in the documentation: "These functions
are intended to be used with binary-mode connections." So I see how using
it on a text connection is undefined, and not a bug. An error or warning
when attempting to use a it on a text connection would be helpful
considering how the behavior has changed in R-3.5.
On Tue, May 29, 2018 at 3:09 AM, Tomas
2009 Oct 20
5
ssh user equivalence
We are getting some pushback from our SA group regarding root having ssh
user equivalence on the cluster where we run OCFS2.
Is it required to have the ssh user equivalence setup for the root user
when running OCFS2 ?
Thanks in advance,
Reid
Reid McKinley
********************************************************************************************
This message, including any
2018 May 26
2
Buffering in R 3.5 connections causes incorrect data in readChar
I noticed an issue where readChar does not return the correct value after a
call to readline. It appears that readChar is not aware of the buffering,
so it reads from the end of the buffer, rather than the current position in
the file. This is a significant change of behavior from R-3.4.4.
Below is a test case that I used to home in on the problem.
---
p<-"test2.txt"
2003 Dec 10
0
C++: SET_LENGTH() Over Many Iterations?
In a C++ extension to R (v 1.8.1), I've been experimenting with a
generic "push back" function to tack one value at a time onto the end
of an R vector created within the extension. After calling this
function a certain number of times Rgui.exe (I'm writing in Windows
using Visual Studio .NET 2003) will fail with an Access Violation,
which doesn't happen when I pre-allocate
2009 Dec 04
0
(PR#14103) read.csv confused by newline characters in
This message is in MIME format. The first part should be readable text,
while the remaining parts are likely unreadable without MIME-aware tools.
--27464147-536455723-1259929222=:18586
Content-Type: TEXT/PLAIN; CHARSET=ISO-8859-15; format=flowed
Content-Transfer-Encoding: 8BIT
Content-ID: <alpine.LFD.2.00.0912041222341.18586 at gannet.stats.ox.ac.uk>
It's not to do with pushback per
2001 Dec 29
1
Slow 'read.table' in R 1.4.0 (PR#1232)
The 'read.table' function appears to be up to 10X slower in R 1.4.0 than R
1.3.1 for some of the data sets I read in. I was comparing the source code
for the 2 versions and see that it was rewritten in R 1.4.0.
I think I found out what part of the problem might be. I was comparing
R1.3.1 and R1.4.0 code and it appears that a statement is missing in some
of the code for R 1.4. This is
2011 Jun 21
2
[LLVMdev] Register class proliferation
In the past, I've seen some pushback on the list against adding more register classes. You can see it in the code as well, TargetLowering::getRegClassForInlineAsmConstraint() returns a vector of registers instead of a real register class.
What is the reason we don't like adding register classes? Is it still a valid reason?
The new register allocators, fast and greedy, don't care at
2019 Jul 18
4
Question about GCC warnings
Hi,
Building LLVM with a newer GCC version seems to generate several compiler warnings, some of which look like false positives. For example, the '-Winit-list-lifetime' warning added in GCC9 triggers for one of the constructors for ArrayRef, the one taking an initializer_list.
How are false positive warnings dealt with in LLVM in general? It's of course possible to just ignore them
2018 May 29
0
Buffering in R 3.5 connections causes incorrect data in readChar
On 05/26/2018 05:15 AM, Aaron Goodman wrote:
> I noticed an issue where readChar does not return the correct value after a
> call to readline. It appears that readChar is not aware of the buffering,
> so it reads from the end of the buffer, rather than the current position in
> the file. This is a significant change of behavior from R-3.4.4.
>
> Below is a test case that I used
2005 Mar 11
0
read.table messes up stdin upon small, erroneous input (PR#7722)
Full_Name: Jan T. Kim
Version: 2.0.1, devel-2005-02-24
OS: Linux 2.6.x
Submission from: (NULL) (139.222.3.229)
Run read.table(stdin()) and type in the broken table
1 2
1
terminating the input by pressing Ctrl-D at the 3rd line of input. An error
message by scan, complaining that "line 2 did not have 2 elements" appears,
as expected. However: After this, there are three empty lines
2011 Jun 21
0
[LLVMdev] Register class proliferation
On Jun 21, 2011, at 8:51 AM, Jakob Stoklund Olesen wrote:
> In the past, I've seen some pushback on the list against adding more register classes. You can see it in the code as well, TargetLowering::getRegClassForInlineAsmConstraint() returns a vector of registers instead of a real register class.
>
> What is the reason we don't like adding register classes? Is it still a valid
2017 Jun 02
6
Providing __dso_handle in LLVM
This is a followup to the discussion that started in D28791. To provide the
context, we need a way to provide __dso_handle in Fuchsia. __dso_handle
symbol is mandated by C++ ABI with a value which is an address in one of
the object's segments, and as such this symbol has to be included
statically and cannot be a part of a shared library. Different systems
provide it differently:
1. On
2008 Sep 26
1
Collecting output from terminal nodes in a recursion tree
I have a recursive function. The recursion forms a tree with many
(millions) terminal nodes. The function must output a value (say, a
number or a vector) from each terminal node. At the end, when all
recursion is done, we want to collect all the output values. How can
that be done cleanly and efficiently?
A prototype example is a recursive function that generates all
permutations of a vector (or