Re: libdar::user_interaction::listing splitting the flag argument

Hi Denis,

Thank you very much for the back-port!
That's the function I was looking for.

I have compiled libdar from git.
By the way, it seems like a #endif in the libdar_config.h include file
is missing:
> #ifndef _DARWIN_USE_64_BIT_INODE
> # define _DARWIN_USE_64_BIT_INODE 1
+ #endif

Unluckily I can list only the root directory ("") of the archive. 
When requesting a subdirectory I get an Exception:
"subdri/ entry does not exist"
Calling get_children_of within the same archive is working as usual.
Can you reproduce this behavior?

Can I only use the get_children_in_table method when working with
archives that had been created with the current git release?
When opening other archives and calling get_children_in_table I ran into
an Exception: 
"it seems to be a bug here"


Regards,
Tobias

Am Freitag, den 25.10.2013, 21:16 +0200 schrieb Denis Corbin:
> On 24/10/2013 20:55, Tobias wrote:
> > Hi Denis,
> 
> Hello Tobias,
> 
> 
> >[...]
> >  
> > 
> > I have another question.
> > 
> > I'm overwrite the listing method to get the output of get_children_of.
> > 
> > Is it possible to break up the "flag" argument into its components?
> 
> Well, I see that there is still room for improvement in this area since
> the libdar/dar split at release 2.0.0.
> 
> In the current development libdar (GIT master) I've added the method
> 
>    archive::get_children_in_table(const std::string & dir) const
> 
> which returns a std::vector of objects of type libdar::list_entry.
> The class list_entry provides all the necessary methods to know about
> the entry of a given directory. This an much more simple alternative to
> get_children_of() method that relies on user_interaction classes.
> 
> references:
> 	src/libdar/archive.hpp 	
> 	src/libdar/list_entry.hpp
> 
> As I cannot tell you when will take place the future major release of
> dar/libdar (release 2.5.0) because there is still important feature to
> add, I have back-ported this feature to the current stable code (GIT
> branch_2.4.x) which will be released with next minor version of
> dar/libdar (release 2.4.12) probably next January unless important bug
> are found in dar/libdar implying a more sooner fix/release.
> 
> You can use this code from GIT branch_2.4.x. If you need to a tarball
> tell me I will send it to you, no problem. But if you prefer you can
> also read the USING_SOURCE_FROM_GIT at the root of the GIT tree on
> branch_2.4.x.
> 
> > 
> > Particularly I'm interested in the "saved" attribute, it is a localised
> > string
> 
> the
> 	list_entry::has_data_present_in_the_archive()
> 	list_entry::is_dirty()
> 
> methods should answer your need.
> 
> > 
> > and thus problematic to work with.
> > 
> > Is there another method implementing this feature?
> > 
> 
> Now, Yes! :)
> 
> >  
> > 
> > Regards,
> > 
> > Tobias
> > 
> >  
> 
> Regards,
> Denis.
> 
> ------------------------------------------------------------------------------
> October Webinars: Code for Performance
> Free Intel webinars can help you accelerate application performance.
> Explore tips for MPI, OpenMP, advanced profiling, and more. Get the most from 
> the latest Intel processors and coprocessors. See abstracts and register >
> http://pubads.g.doubleclick.net/gampad/clk?id=60135991&iu=/4140/ostg.clktrk
> _______________________________________________
> Dar-libdar_api mailing list
> [email protected]
> https://lists.sourceforge.net/lists/listinfo/dar-libdar_api



------------------------------------------------------------------------------
October Webinars: Code for Performance
Free Intel webinars can help you accelerate application performance.
Explore tips for MPI, OpenMP, advanced profiling, and more. Get the most from 
the latest Intel processors and coprocessors. See abstracts and register >
http://pubads.g.doubleclick.net/gampad/clk?id=60135991&iu=/4140/ostg.clktrk