search for: sstream

Currently we (attempt to) support building Xapian with any GCC >= 2.95. However, I only have access to Debian's GCC "2.95.4" (which is 2.95.3 plus patches) and <sstream> was added in GCC 2.95.3, so the fallback code for when <sstream> isn't available probably hasn't actually been exercised for a while. I'm pretty sure the non-<sstream> build is now broken in SVN HEAD, but ensuring it's fixed would require building a suitable old rel...

...sembly version of the instruction instead of the name, which makes things a bit clearer. Is this ok to commit? I've two doubts here. First, was there a particular reason to not do this in the first place? Performance perhaps? Shouldn't matter so much, I guess? Second, I'm including <sstream> directly. Is this allowed, or should there be some LLVM wrapper just as for <iostream> ? (Code was copied from instcombine, though). Gr. Matthijs Index: CrashDebugger.cpp =================================================================== --- CrashDebugger.cpp (revision 54012) +++ Cr...

...es.c:263 ctx = {type = LOG_TYPE_PANIC, exit_status = 0, timestamp = 0x0} args = {{gp_offset = 40, fp_offset = 48, overflow_arg_area = 0x7fff5fba6e40, reg_save_area = 0x7fff5fba6d80}} #5 0x00007fea0d786bb8 in i_stream_seekable_read (stream=0xd658a0) at istream-seekable.c:253 sstream = 0xd658a0 data = 0x7fff5fba6ea0 "\320n\272_\377\177" size = 14047392 pos = 27457 ret = 139638205298784 __FUNCTION__ = "i_stream_seekable_read" #6 0x00007fea0d77e866 in i_stream_read (stream=0xd65900) at istream.c:149 _stream = 0x...

Hello, All! I have function which is written in C, the function uses other functions also builded bu me. Now I need to use the function to build R function. My questions are: 1. How can I include libraries (for example, iomanip, sstream, tcl.h)? 2. Should I put other function to the separate file and then include the file? Thanks All :) Olga [[alternative HTML version deleted]]

...'stringio.rbw'' -- small sample for it. Short usage: stream = Wx::StringInputStream.new image_data image = Wx::Image.new stream stream = Wx::StringOutputStream.new image.save_file stream, ''image/jpeg'' image_data = stream.get_string Installation: just place ''sstream.cpp'' and ''sstream.in'' in ''src'' and add ''sstream.o'' to $objs variable in ''src/extconf.rb''. -- Dmitry mailto:dmiceman@ubiz.ru _______________________________________________ wxruby-users ma...

...earer. > Is this ok > to commit? Cool, sure, looks fine with one change. > I've two doubts here. First, was there a particular reason to not do > this in > the first place? Performance perhaps? Shouldn't matter so much, I > guess? > Second, I'm including <sstream> directly. Is this allowed, or should > there be > some LLVM wrapper just as for <iostream> ? (Code was copied from > instcombine, though). <iostream> is the only "poisoned" header, all other stream headers are ok. Also, for bugpoint, we don't really care...

Hello, All! I'm new for R-devel list. And I'd like to ask some questions, maybe they will be stuped for the most part of members of the list. I need to call function which is written in C++ from R. My questions are: 1. How should I include libraries (for example, iomanip, sstream, iostream)? 2. Can I use namespace? Thanks All :) Olga

...>, msgid=: save failed to INBOX: BUG: Unknown internal error --- This "write_full() failed" from: src/lib/istream-seekable.c --- static ssize_t i_stream_seekable_read(struct istream_private *stream) { ... /* save to our file */ data = i_stream_get_data(sstream->cur_input, &size); if (write_full(sstream->fd, data, size) < 0) { i_assert(errno != 0); stream->istream.stream_errno = errno; i_error("write_full(%s) failed: %m",...

...works as expected in R-2.5.0. I get the problem with two different operating systems - an older redhat and new ubuntu and with both g++4.1 and g++3.4. I have a problem with character data that is passed back from C++ code. A small example is the following C++ code and R functions. #include <sstream> extern "C" { void extracttxt( char **txt, int *nchars) { std::ostringstream oss; oss << "abcdefghij"; const char *ltxt=oss.str().c_str(); for (int j=0;j<*nchars;j++) *txt[j]=static_cast<char>(ltxt[j]); } } # begin R code dy...

...__FUNCTION__ = "i_stream_qp_decoder_read" #11 0x00007f9d1bce6de9 in i_stream_read (stream=0x66ddb0) at istream.c:135 _stream = 0x66dd50 old_size = 0 ret = <optimized out> __FUNCTION__ = "i_stream_read" #12 0x00007f9d1bcebcac in read_more (sstream=0x66df30) at istream-seekable.c:140 size = <optimized out> ret = <optimized out> #13 0x00007f9d1bcebe59 in read_from_buffer (sstream=sstream at entry=0x66df30, ret_r=ret_r at entry=0x7fff684222c8) at istream-seekable.c:182 stream = 0x66df30 data = <opt...

they are the same for practical purposes, but I believe i started pushing m3u because it was better supported, or less application fought over it, or something. it's probably different today, but i still use m3u. M3U is simpler than pls. just a file/url per line, that's it. for a sstream a pls file would look like: http://your.server.com:8000/mymount and that's it. jack. On Thu, Apr 12, 2001 at 04:25:56PM -0400, Steve Glines wrote: > I tried a pls file and it appears to work. What's the difference (in > practical terms) and where do I find the documentation on M3U...

..._? before ?namespace? covmodel.h:20: error: expected ?=?, ?,?, ?;?, ?asm? or ?__attribute__? before ?covmodel? util.h:12:20: error: iostream: No such file or directory util.h:13:19: error: iomanip: No such file or directory util.h:14:18: error: string: No such file or directory util.h:15:19: error: sstream: No such file or directory util.h:16:18: error: vector: No such file or directory util.h:17:15: error: map: No such file or directory util.h:18: error: expected ?=?, ?,?, ?;?, ?asm? or ?__attribute__? before ?namespace? util.h:20:15: error: R.h: No such file or directory util.h:21:19: error: Rmath....

Hi me (2x - Haberman and Coalson), On Tue, Nov 11, 2003 at 03:51:42PM -0800, Josh Coalson wrote: > The C++ interface is a little simpler: [code follows] OK. Well, I found the C interface a little bit easier to understand, so I ended up using that instead of continuing to try to figure out the C++ interface. The one problem I have is that the values in block->data. vorbis_comment.comments

.../\245"... bytes_sent = false ret = 32766 __FUNCTION__ = "openssl_iostream_bio_output" #10 0x00007f8bb12d6af6 in openssl_iostream_bio_sync (ssl_io=0x220aa00) at iostream-openssl.c:459 ret = false #11 0x00007f8bb12da52e in o_stream_ssl_flush_buffer (sstream=0x220aca0) at ostream-openssl.c:110 pos = 6 ret = 6 #12 0x00007f8bb12da6ef in o_stream_ssl_sendv (stream=0x220aca0, iov=0x7ffef81dcd70, iov_count=1) at ostream-openssl.c:155 sstream = 0x220aca0 bytes_sent = 6 #13 0x00007f8bb657e765 in o_stream_sendv (stream=0x2...

.../\245"... ???????? bytes_sent = false ???????? ret = 32766 ???????? __FUNCTION__ = "openssl_iostream_bio_output" #10 0x00007f8bb12d6af6 in openssl_iostream_bio_sync (ssl_io=0x220aa00) at iostream-openssl.c:459 ???????? ret = false #11 0x00007f8bb12da52e in o_stream_ssl_flush_buffer (sstream=0x220aca0) at ostream-openssl.c:110 ???????? pos = 6 ???????? ret = 6 #12 0x00007f8bb12da6ef in o_stream_ssl_sendv (stream=0x220aca0, iov=0x7ffef81dcd70, iov_count=1) at ostream-openssl.c:155 ???????? sstream = 0x220aca0 ???????? bytes_sent = 6 #13 0x00007f8bb657e765 in o_stream_sendv (stream=0x2...

...sl_iostream_more (ssl_io=ssl_io at entry=0x5646c0a22aa0, type=type at entry=OPENSSL_IOSTREAM_SYNC_TYPE_HANDSHAKE) at iostream-openssl.c:546 ret = <optimized out> #9 0x00007fb7bb85a30f in i_stream_ssl_read_real (stream=stream at entry=0x5646c0a5b530) at istream-openssl.c:46 sstream = 0x5646c0a5b530 ssl_io = 0x5646c0a22aa0 buffer = "\234y\345h\226#a\256*\v\216\024\215\250S\227\362\300\003\231\212\027\361\340\353vfv\206_\375\340\362\300\003\231\212\027\361\340\353vfv\206_\375\340kEt`6\005\235\273\205\365\211\366\bU\374\212kEt`6\005\235\273\205\365\211\36...

...ssors.cpp b/src/processors.cpp index 4317b1f..30a2837 100644 --- a/src/processors.cpp +++ b/src/processors.cpp @@ -17,25 +17,19 @@ * also available at http://www.gnu.org/copyleft/gpl.html. */ -#include <iostream> +#include "processors.h" #include <fstream> -#include <sstream> -#include <string> -#include <vector> -#include <stdexcept> - -#include <hal/libhal.h> - +#include <iostream> #include <pcre.h> -#include "hal.h" -#include "processors.h" +// TODO remove this wrapper once rhbz#583747 is fixed +extern &q...

So by now you have already seen this, but just in case you have not: ============= Note that using the other stream headers (<sstream> for example) is not problematic in this regard — just <iostream>. However, raw_ostream provides various APIs that are better performing for almost every use than std::ostream style APIs. Therefore new code should always use raw_ostream for writing, or the llvm::MemoryBuffer API for readin...

...an overhead in each compilation unit due to it needing to make sure that all of the std::c* streams are constructed first. This is a terrible waste of resources and one which we can do without. The changes should be pretty transparent. There may be a few places which need a hack to support sstreams. This will be solved in the future. Here's what the changes are: Old Way New Way ------- ------- #include <iostream> #include "llvm/Support/Streams.h" or class llvm_ostream; // forward declaration std::cout llvm_cout std::cerr llvm_cerr std::cin l...

Hi, Under gcc 2.95 Xapian fails to build like so: g++ -DHAVE_CONFIG_H -I. -I./common -I./include -I/home/dsainty/not-backed-up/pkgsrc/textproc/xapian/work/.buildlink/include -Wall -W -Wredundant-decls -Wpointer-arith -Wcast-qual -Wcast-align -Wno-long-long -Wformat-security -fno-gnu-keywords -Wundef -O2 -c queryparser/queryparser_internal.cc