Hello Julia,

I described some progress in my last report but I didn't get answer
from you. Did you do any test?  Have you met any problem with my code?

Sorry for the recent latency of my replies to your emails, the last couple of weeks were quite busy for me. But I still plan to reply to your previous emails eventually.

Frankly, I didn't see any urgent outstanding questions or queries in your previous report that I should reply to immediately. I thought that you were only describing steady state progress and the usual issues that you deal with as you go.

I am sorry if this was a misunderstanding on my side. Next time, you should perhaps consider formulating queries more directly, as proper questions that catch one's attention.

Can I
disregard to saving of memory for more readable implementation?  My
implementation could be close to function udf_read_fid_in_data.

I agree with Jakub here: The goal is _never_ to have a hyper-optimized hyper-complicated code, sacrificing readability. Especially if you are working on an initial implementation which needs to be properly tested and debugged first.

A straightforward, clean, readable and understandable solution is always preferred in such cases, even if it is suboptimal. Once you know that the implementation works correctly, you (or someone following your code) can start to optimize it. But premature optimization usually does more harm than good.

Speaking more specifically: I believe that the need to read the directory entries of a directory from potentially multiple sectors is not an unusual requirement. Many other file systems (even FAT) store directories just like other files, potentially fragmented and in multiple sectors.

Simply implement a generic directory read operation which can live with the fact that the directory entries are stored in multiple non-consecutive sectors, even if it requires some memory copying. You can take inspiration from the other file system drivers in HelenOS how to implement this.

I had to change time of my holiday.  I am not very happy that it
before midterm and I worry about my results. Have I good progress for
midterm or not? If not what I should do to pass it?

Please do not take this as a definitive official answer, I plan to spend more time on evaluating your code and overall progress during the midterm evaluation period.

But at the first glance it appears to me that you are on track and therefore your chances to pass the midterm evaluation are pretty high.


M.D.

_______________________________________________
HelenOS-devel mailing list
[email protected]
http://lists.modry.cz/cgi-bin/listinfo/helenos-devel

Reply via email to