I really get the point, and what I should have been doing. Anyways shit happens!<br><br>Thanks for the answers though.<br><br><div class="gmail_quote">2009/11/22 Svein Ove Aas <span dir="ltr"><<a href="mailto:svein.ove@aas.no">svein.ove@aas.no</a>></span><br>
<blockquote class="gmail_quote" style="border-left: 1px solid rgb(204, 204, 204); margin: 0pt 0pt 0pt 0.8ex; padding-left: 1ex;"><div class="im">On Sun, Nov 22, 2009 at 1:04 AM, Uwe Hollerbach <<a href="mailto:uhollerbach@gmail.com">uhollerbach@gmail.com</a>> wrote:<br>
> Ouch... my condolences, but I think you're screwed. I think the .hi<br>
> files are purely interface info, and the .o files have all the info on<br>
> what to actually do (and getting to .hs files from .hi+.o is gonna be<br>
> like going from sausage to pig, in any case). If you haven't messed<br>
> with the disk, I think your best bet might be to try and undelete<br>
> files. That might be as messy as looking at the raw disk image and<br>
> trying to recover disk sectors, or possibly there are still entire<br>
> files there that are just not referenced by directory entries. Either<br>
> (or any) way, it's a bit chancy...<br>
><br>
</div>And this why you always, *always* use a revision-control system or at<br>
least good backups.<br>
<br>
.hi files actually do contain some code, specifically what ghc decides<br>
can be inlined (see ghc --show-iface), but it's not the sort of code<br>
you'd get any use from. Have a look, you'll see.<br>
<br>
--<br>
<font color="#888888">Svein Ove Aas<br>
</font></blockquote></div><br><br clear="all"><br>-- <br>Ozgur Akgun<br>