Hi Matt 2011/6/2 mattschinkel <[email protected]> > > I'm happy to see you using aliases! This means hard disk will work as > well. >
Yes it should > > I see you decided to put the aliases in the sample, but I had put them > in the library. What should the standard be? Maybe we should create a > seperate lib for "drivers"? > I don't like aliases within libs, because it's putting "foreign" concepts from the lib point of view (filesystem doesn't have to know about underlying storage). "driver" libs could be a good idea, but for now I prefer to stick to current implementation (which isn't done as file/dir creation/deletion aren't supported) > > I haven't noticed what implementation you used. Do you read entire > sectors with sd_read_sector, or do you use sd_data_byte? If you use > only one, you will save space. I had actually decided to use > sd_read_sector_address. > I act on sector as a whole. First implemenation used sd_data_byte, but it just didn't work when it comes to actually writing data. So I had to switch to sector read/write. > > Also, why are the Minux command constants in the sample instead of the > lib? > Because they have nothing to do in the lib :) minix_cmd.jal declares useful, common commands as API, not as an interpreter. Sample implements a REPL, which match constants with API. Cheers, Seb -- You received this message because you are subscribed to the Google Groups "jallib" group. To post to this group, send email to [email protected]. To unsubscribe from this group, send email to [email protected]. For more options, visit this group at http://groups.google.com/group/jallib?hl=en.
