On 5/12/16, Andy Goth wrote:
> How about variable naming? I see a kind of Hungarian notation is widely
> but not universally used. I tried to match it where I could figure what
> made sense.
>
Trying to match existing code is the best approach.
I agree that it would be good to document variab
On 5/12/2016 9:47 AM, Richard Hipp wrote:
> On 5/12/16, Andy Goth wrote:
>> I'm looking for fiddly bits like placement of spaces adjacent to
>> parentheses, braces, and operators; also how to indent overlong logical
>> source lines continued across multiple physical source lines.
>
> We don't hav
On 5/12/16, Andy Goth wrote:
>
> I'm looking for fiddly bits like placement of spaces adjacent to
> parentheses, braces, and operators; also how to indent overlong logical
> source lines continued across multiple physical source lines.
>
We don't have any documentation on the fiddly details. Try
On 5/12/2016 9:02 AM, Richard Hipp wrote:
> On 5/12/16, Andy Goth wrote:
>> Is there a documented preferred style for Fossil coding?
>
> https://www.fossil-scm.org/fossil/doc/trunk/www/style.wiki
>
> The above could perhaps be augmented.
Thanks. That's pretty much all stuff I do anyway though
On 5/12/16, Andy Goth wrote:
> Is there a documented preferred style for Fossil coding?
https://www.fossil-scm.org/fossil/doc/trunk/www/style.wiki
The above could perhaps be augmented.
--
D. Richard Hipp
d...@sqlite.org
___
fossil-dev mailing list
fo
On 5/2/2015 4:49 PM, Richard Hipp wrote:
> On 5/2/15, Andy Goth wrote:
>> I have a hard time locating where functions are defined, as opposed to
>> where they are prototyped or used. Yeah I know I could use ctags or
>> such, but I prefer simple greps when possible.
>
> You could use "grep '^[a-z]
On 5/2/15, Andy Goth wrote:
> I have a hard time locating where functions are defined, as opposed to
> where they are prototyped or used. Yeah I know I could use ctags or
> such, but I prefer simple greps when possible.
>
> There are a few stylistic techniques to make it easy to find a function
>
