<?xml version="1.0" encoding="utf-8"?>
<feed xml:lang="en" xmlns="http://www.w3.org/2005/Atom"><title>Recent changes to feature-requests</title><link href="https://sourceforge.net/p/scribeserver/feature-requests/" rel="alternate"/><link href="https://sourceforge.net/p/scribeserver/feature-requests/feed.atom" rel="self"/><id>https://sourceforge.net/p/scribeserver/feature-requests/</id><updated>2009-06-06T03:09:27Z</updated><subtitle>Recent changes to feature-requests</subtitle><entry><title>Improve build support for hadoop</title><link href="https://sourceforge.net/p/scribeserver/feature-requests/3/" rel="alternate"/><published>2009-06-06T03:09:27Z</published><updated>2009-06-06T03:09:27Z</updated><author><name>Anthony Giardullo</name><uri>https://sourceforge.net/u/agiardullo/</uri></author><id>https://sourceforge.net07d2810bd06a1a449fdec8baff25a968cac1b1c6</id><summary type="html">&lt;div class="markdown_content"&gt;&lt;p&gt;Currently, in order to build Scribe with Hadoop support (--enable-hdfs), you need to specify the CPPFLAGS/LDFLAGS manually to build/link with java and hdfs.    Eg:&lt;/p&gt;
&lt;p&gt;./configure --with-hadooppath=/usr/local/hadoop --enable-hdfs  CPPFLAGS="-I/usr/local/java/include -I/usr/local/java/include/linux" LDFLAGS="-ljvm -lhdfs"&lt;/p&gt;
&lt;p&gt;It would be nice to add some intelligent autoconf macros to clean this up.&lt;/p&gt;&lt;/div&gt;</summary></entry><entry><title>Remove dependency on Boost Filesystem</title><link href="https://sourceforge.net/p/scribeserver/feature-requests/2/" rel="alternate"/><published>2009-02-24T01:09:41Z</published><updated>2009-02-24T01:09:41Z</updated><author><name>Anthony Giardullo</name><uri>https://sourceforge.net/u/agiardullo/</uri></author><id>https://sourceforge.net178fdf0d252628bdd8ccccdf687e886e6511d99a</id><summary type="html">&lt;div class="markdown_content"&gt;&lt;p&gt;Scribe currently uses the Boost Filesystem library so that filesystem operations are platform independent.  But this requires that users link with the Boost System and Filesystem libraries.&lt;br /&gt;
&lt;/p&gt;
&lt;p&gt;If we removed this dependency, Scribe would not need to be linked with any Boost libraries.  Scribe would still need Boost because it heavily uses Boost Shared Pointers.  However this is implemented using included header files only.  So Scribe would just need to be compiled with the boost headers.&lt;/p&gt;
&lt;p&gt;If we just used posix file operations instead, Scribe would still be pretty portable.  And if anyone wanted to run Scribe on say Windows, they would just need to make sure they have posix support (eg Cygwin or something similar).&lt;/p&gt;&lt;/div&gt;</summary></entry><entry><title>Remove unnecessary null pointer checks</title><link href="https://sourceforge.net/p/scribeserver/feature-requests/1/" rel="alternate"/><published>2008-10-27T15:11:06Z</published><updated>2008-10-27T15:11:06Z</updated><author><name>Markus Elfring</name><uri>https://sourceforge.net/u/elfring/</uri></author><id>https://sourceforge.netcedde61fd98036cbcef54362ec9a0d92b2065596</id><summary type="html">&lt;div class="markdown_content"&gt;&lt;p&gt;Null pointer checks for member variables like "pcategory_prefixes" and "inputBuffer" are not needed for the delete instruction.&lt;br /&gt;
&lt;a href="http://dietmar-kuehl.de/mirror/c++-faq/freestore-mgmt.html#faq-16.8" rel="nofollow"&gt;http://dietmar-kuehl.de/mirror/c++-faq/freestore-mgmt.html#faq-16.8&lt;/a&gt;&lt;br /&gt;
&lt;a href="http://scribeserver.svn.sourceforge.net/viewvc/scribeserver/trunk/src/scribe_server.cpp?revision=3&amp;amp;view=markup"&gt;http://scribeserver.svn.sourceforge.net/viewvc/scribeserver/trunk/src/scribe_server.cpp?revision=3&amp;amp;view=markup&lt;/a&gt;&lt;br /&gt;
&lt;a href="http://scribeserver.svn.sourceforge.net/viewvc/scribeserver/trunk/src/file.cpp?revision=3&amp;amp;view=markup"&gt;http://scribeserver.svn.sourceforge.net/viewvc/scribeserver/trunk/src/file.cpp?revision=3&amp;amp;view=markup&lt;/a&gt;&lt;/p&gt;
&lt;p&gt;Can smart pointers like std::auto_ptr or boost::shared_ptr help in this use case?&lt;/p&gt;&lt;/div&gt;</summary></entry></feed>