[openbeosstorage] Re: BSymLink tests and check_*_name() added

On Fri, 19 Apr 2002, Tyler Dauwalder wrote:

> > Since I guess, I will finish the BSymLink implementation tomorrow, I'm

I guess, I was too optimistic. I mean, I kind of finished it indeed, but
it was by far not as easy as it seemed to be.

Apparently there is no (publicly available) functionality to read a
symlink's contents having only its file descriptor at hand.
As a work-around, now a BSymLink owns a BEntry that is set/unset whenever
the SetTo()/Unset() is invoked on the BSymLink object. Since BSymLink
originally  didn't implement these methods, but let BNode do the work
(BTW, some BNode::SetTo() version were unimplemented, thus I filled them
in), the linking of the R5 test app broke.
Well, finally, after getting familiar with Jam, I was able to get the two
sets of tests compiled with their respective headers and now everything
works again. :-)


> > My only problem is, that I don't have any resources about resources. ;-)
> > Has anyone an idea, how to cope with my lack of knowledge?
> 
> I'm afraid I don't. I did a tiny bit of looking around and came up with 
> nothing. If worst comes to worse we may be able to figure it out by playing 
> around with QuickRes and watching what happens to the executable when we 
> add, rename, remove resources, etc.
> 
> We should see if anyone on the main OpenBeOS list or BeDevTalk could be of 
> any help, though. 

Yep, I will post a message.

> > Or, Tyler, do you want me rather to help you with BEntry or BPath, so
> > that we get the core classes done faster?
> 
> Actually, yes. Why don't you take over BPath? I'm basically done with 
> BEntry, but I need to round out the tests for it quite a bit. Plus I'm 
> finding myself a bit short on free time this quarter.

Alright, then I start fighting with BPath.
Afterwards I would like to attack BResources (unless someone objects).
That is we might want to run a more thorough cleanup iteration on the core
classes before.

CU, Ingo

Other related posts: