Displaying 20 results from an estimated 1000 matches similar to: "Need 64-bit integers on 32-bit platform"
2002 Mar 05
3
reading 2-byte integers using readBin and connections
Hi folks:
This may be a stupid question, but I cannot seem to find a way to tell
readBin that I want to read 2-byte integers from the connection. The input
file is 150,720 bytes long containing 75,360 short (2-byte) integers. But
specifying "integer" or "int" for what in readBin only returns me a vector
of length 37680, leading me to believe that sizeof(integer) or
2003 Jun 13
2
problem with libc_r (uthread_close.c) in 4.8-STABLE
Unsure what exactly the problem is, but when using 4.8-STABLE I was unable
to compile MySQL (it failed during configure phase)..
On further investigation, the following code segment when compiled with
phtreads, results in a segmentation fault:
#include <stdio.h>
typedef long long longlong;
main()
{
longlong ll=1;
float f;
FILE *file=fopen("conftestval", "w");
f
2011 Mar 29
2
Reading 64-bit integers
Dear all,
I see from some previous threads that support for 64-bit integers in R
may be an aim for future versions, but in the meantime I'm wondering
whether it is possible to read in integers of greater than 32 bits at
all. Judging from ?readBin, it should be possible to read 8-byte
integers to some degree, but it is clearly limited in practice by R's
internally 32-bit integer type:
2009 Aug 03
1
[PATCH] Remove files imported via autogen.sh.
In case you're ok with not version-controlling files imported
via autogen, ...
>From 72c829395bb6a4800516d4f535e18af48195585b Mon Sep 17 00:00:00 2001
From: Jim Meyering <meyering at redhat.com>
Date: Mon, 3 Aug 2009 11:00:22 -0400
Subject: [PATCH] Remove files imported via autogen.sh.
* m4/.gitignore: Ignore these files.
* m4/codeset.m4: Remove file.
* m4/gettext.m4: Likewise.
*
2009 May 18
2
readBin on binary non-blocking connections (Windows & Unix differences/bugs)
R-devel:
I am encountering a consistency issue using socketConnection and
readBin with *non-blocking* connections on Unix and Windows XP (no
Vista to test).
I am a bit confused by the behavior of *non-blocking* connections
under Windows specifically. When calling readBin on a non-blocking
connection when there is no data to read on the socket, the connection
under Unix will return a vector of
2006 Jun 28
2
read file with readBin (the file was saved with a C-routine)
Hello!
I have problems with using of "readBin" to read files, which was written in C with "fwrite". In the C-File there is the following Code:
fwrite(MyitINI,sizeof(itINItype),1,outfile);
where MyitINI is a structure of the following form
typedef struct{
int KernelFileSave; /* Determined, if Systemmatrix saved or not.*/
char KernelFileName[200]; /* A-Matrix name
2019 Dec 18
0
readBin should check that its endian argument is a legal value
Thank you for reporting this problem, R-devel now has a check in readBin
and writeBin.
I've identified two CRAN packages with an incorrect value for "endian"
and reported to maintainers, unfortunately in their case the intention
was to specify "little".
Best
Tomas
On 11/18/19 11:22 PM, Jennifer Lyon wrote:
> I think it would be helpful if readBin checked that its
2004 Jun 01
2
Importing binary data
Hi everybody!
I've a large dataset, about 2 Mio entries of the format which I would like
to import into a frame:
<integer><integer><float><string><float><string><string>
Because to the huge data amount I've choosen a binary format instead
of a text format when exporting from Matlab.
My import function is attached below. It works fine for only
2005 Jan 21
1
rsync compilation
Hi all
Here is the egrep result :
egrep "SIZEOF|LONGLONG" build_mipsel/rsync-2.6.3/config.h
/* #undef HAVE_LONGLONG */
#define SIZEOF_INT 4
#define SIZEOF_LONG 4
#define SIZEOF_SHORT 2
and the HAVE_LONGLONG config.log result :
rsync_cv_HAVE_LONGLONG=cross
Is there a problem with this values ?
Thanks a lot for your answer
Best regards, Florian
2007 Jan 26
1
readBin is much slower for raw input than for a file
Dear all,
I'm trying to write an efficient binary file reader for a file type
that is made up of several fields of variable length, and so requires
many small reads. Doing this on the file directly using a sequence of
readBin() calls is a bit too slow for my needs, so I tried buffering
the file into a raw vector and reading from that ("loc" is the
equivalent of the file pointer):
2007 Jan 26
1
readBin is much slower for raw input than for a file
Dear all,
I'm trying to write an efficient binary file reader for a file type
that is made up of several fields of variable length, and so requires
many small reads. Doing this on the file directly using a sequence of
readBin() calls is a bit too slow for my needs, so I tried buffering
the file into a raw vector and reading from that ("loc" is the
equivalent of the file pointer):
2013 May 08
1
getting corrupted data when using readBin() after seek() on a gzfile connection
Hi,
I'm running into more issues when reading data from a gzfile connection.
If I read the data sequentially with successive calls to readBin(), the
data I get looks ok. But if I call seek() between the successive calls
to readBin(), I get corrupted data.
Here is a (hopefully) reproducible example. See my sessionInfo() at the
end (I'm not on Windows, where, according to the man page,
2013 Dec 13
0
how to use the readBin ?
how to use the readBin ?
i want to write the extended ascii character `Œ` into a file named c:/testbin,
and read it in the R console ,display it as `Œ` in R console.
now i can write it .
zz <- file("c:/testbin", "wb")
writeBin(charToRaw("\u0152"), zz)
close(zz)
when i open the file with office(encoding=utf-8),i can see `Œ`,whay i can not read it with readBin?
2009 Feb 11
0
More help with Binary Files
Does anyone else have any insights to this issue:
Henrick, thank you for your very quick response. I've examined the readBin
help file with respect to endian and I'm still not sure I'm getting this
correct.
Here is what I'm coding:
con <- file(file.choose(), open="rb")
Year66 <- readBin(con, what=integer(), signed = TRUE, size = 2,
endian="little", n
2006 Nov 07
1
reading VERY large binary files
Hello,
I am trying to read in elements out of a very large binary file ... the
total file is 4 gigs. I want to select rows out of the file, and the
current procedure I run works but is prohibitively slow (takes more than
a day to run and still won't complete). Is there any faster way to
accomplish this?
My current procedure looks like this:
readHH <- function(file_name,
2007 Jun 12
1
Can strptime handle milliseconds or AM/PM?
I'm trying to proess date/time fields from files that were given to me to
analyze.
Any clues what I'm doing wrong with strptime? This seems to fail the same
way under Linux or Windows.
For ?strptime would it make sense to explain %OS3 somewhere besides the
Examples?
> # Why does %OS3 work here?
> format(Sys.time(), "%H:%M:%S")
[1] "16:45:19"
>
2007 Jul 08
0
patch to enhance sound module for 96 kHz/24 bit sample sizes
Greetings Matthias,
Thanks again for your sound module. I did not ever manage to find the
time to play with phase equations, but I found I needed the module for a
new project involving bats. I needed to do some work @ 96 kHz/24 bit
sample size, and found the limitations of the sound package stop at 48
kHz and 16 bit samples. Here's a patch to bring things up to 96/24.
Sorry I cannot
2006 Jun 02
1
Typo fix for readBin.Rd
Hi,
The man page for readBin has a small typo:
--- a/src/library/base/man/readBin.Rd
+++ b/src/library/base/man/readBin.Rd
@@ -58,7 +58,7 @@ writeBin(object, con, size = NA, endian
\code{readBin} and \code{writeBin} read and write C-style
zero-terminated character strings. Input strings are limited to 10000
- characters. \code{\link{readChar}} and \code{\code{writeChar}}
+
2007 Dec 31
1
readBin differences on Windows and Linux/mac
I have been trying to use the gunzip function in the R.utils package. It
opens a connection to a gzfile, uses readBin to read from that connection,
and then uses writeBin to write out the raw data to a new file. This works
as expected under linux/mac, but under Windows, I get:
Error in readBin(inn, what= raw(0), size = 1, n=BFR.SIZE) :
negative length vectors are not allowed
A simple
2019 Nov 18
2
readBin should check that its endian argument is a legal value
I think it would be helpful if readBin checked that its endian argument is
a legal value.
Why? I was reviewing some of our code and noticed that the author had
readBin(..., endian="network") and never having heard of "network", I
looked at the man page for readBin, and it hadn't heard of "network"
either. Not good.
I then looked at the R code for readBin, which