[haiku-development] Re: Haiku Coding Guidelines Issues
- From: "Euan Kirkhope" <euan.kirkhope@xxxxxxxxxxxxxx>
- To: haiku-development@xxxxxxxxxxxxx
- Date: Thu, 6 Sep 2007 09:15:13 +0100
On 05/09/07, Jordan Walsh <jordanwalsh@xxxxxxxxx> wrote:
> I am also not a developer but I keep an eye on the mailing lists. It took me
> a long time to get out of the habit of saying "char* foo" rather than "char
> *foo" because when i read that line i translate it to "pointer to a
> character named foo". It was the way I was taught and has taken some
> practice to fix.
>
Time wasted if you ask me. I'll always do char* foo, and will never
change. I've rarely declared multiple variables on a line, especially
pointers so it's not an issue.
Euan
:p
- Follow-Ups:
- [haiku-development] Re: Haiku Coding Guidelines Issues
- From: Jordan Walsh
- References:
- [haiku-development] Haiku Coding Guidelines Issues
- From: Ryan Leavengood
- [haiku-development] Re: Haiku Coding Guidelines Issues
- From: Ingo Weinhold
- [haiku-development] Re: Haiku Coding Guidelines Issues
- From: Truls Becken
- [haiku-development] Re: Haiku Coding Guidelines Issues
- From: Jordan Walsh
Other related posts:
- » [haiku-development] Haiku Coding Guidelines Issues
- » [haiku-development] Re: Haiku Coding Guidelines Issues
- » [haiku-development] Re: Haiku Coding Guidelines Issues
- » [haiku-development] Re: Haiku Coding Guidelines Issues
- » [haiku-development] Re: Haiku Coding Guidelines Issues
- » [haiku-development] Re: Haiku Coding Guidelines Issues
- » [haiku-development] Re: Haiku Coding Guidelines Issues
- » [haiku-development] Re: Haiku Coding Guidelines Issues
- [haiku-development] Re: Haiku Coding Guidelines Issues
- From: Jordan Walsh
- [haiku-development] Haiku Coding Guidelines Issues
- From: Ryan Leavengood
- [haiku-development] Re: Haiku Coding Guidelines Issues
- From: Ingo Weinhold
- [haiku-development] Re: Haiku Coding Guidelines Issues
- From: Truls Becken
- [haiku-development] Re: Haiku Coding Guidelines Issues
- From: Jordan Walsh