[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]
Re: [PATCH] Respect outfile
- Subject: Re: [PATCH] Respect outfile
- From: Ori Bernstein <ori@xxxxxxxxxxxxxx>
- Date: Thu, 15 Jan 2015 14:25:11 -0800
- To: Ryan Gonzalez <rymg19@xxxxxxxxx>
- Cc: myrddin-dev@xxxxxxxxxxxxxx
Figured out git-am and applied it; next time, one plain text email per patch should work best.
Also, fixed one small bug: strncpy() doesn't null terminate. snprintf() is preferred. And yes, C string handling functions suck.
On Jan 15, 2015, at 12:22 PM, Ryan Gonzalez <rymg19@xxxxxxxxx> wrote:
> I'm not sure what Myrddin's contributing guidelines are, so I'm doing things the hg-git way of sending the patch to the mailing list.
>
> This is really simple: it just actually uses outfile. If someone specifies an output file, then it will be used as the output for the object file; the output's basename will also be used for the use file and the assembler file (if -S was passed).
>
> Another patch is attached that fixes a slight logic error in the man page that confused me very much. :)
>
> --
> Ryan
> If anybody ever asks me why I prefer C++ to C, my answer will be simple: "It's becauseslejfp23(@#Q*(E*EIdc-SEGFAULT. Wait, I don't think that was nul-terminated."
> Personal reality distortion fields are immune to contradictory evidence. - srean
> Check out my website: http://kirbyfan64.github.io/
> <patch.diff><man.diff>