Okay I am EXTREMELY HAPPY with my upcoming 3-part article on "Reading Files The Hard Way". It's - in total - a 60 minute read (if you don't dilly dally), and it contains some extremely cool Rust code.pic.twitter.com/iVGmdi9v9i
U tweetove putem weba ili aplikacija drugih proizvođača možete dodati podatke o lokaciji, kao što su grad ili točna lokacija. Povijest lokacija tweetova uvijek možete izbrisati. Saznajte više
The C examples never free() their malloc()'d memory. Is that intentional?
sure - the OS cleans up for us on process exit. This isn't the first nitpick I've gotten on this otherwise exploratory/throwaway code!
Heh. "It is extremely expensive for tape drives." So if there were a file system format specifically designed for this, a "tape archive" format, so to speak, it probably doesn't work this way, right? (Ah, well, it works well enough for the common 'extract the whole thing' case)
Yeah I'm of two minds about TAR because on one hand, full-stream compression yields great results, and on the other, I *really* like random access and there's just no way that's happening with TAR (even generating an index file would be hard!)
Have you ever tried to print (PDF-ize) one of your blog entries? Now I will never know how to read a file!!
Twitter je možda preopterećen ili ima kratkotrajnih poteškoća u radu. Pokušajte ponovno ili potražite dodatne informacije u odjeljku Status Twittera.