Yes, as the logging functions are inline/macros it will be easy, the
file:function:line on debug level (maybe normal output as well) would be
fine I guess.
This is why I added layer name in my log output at some point as a separate
commit, modification of logging function is on my todo list but I did not
want to introduce it right now because there are already enough changes to
cause misunderstandings ;-)
Regsrding the directory structure is similar as above - at first I wanted
to make flat directory structure of a functionality and use prefix fo mark
what part of the code is there (something like current Target
organization), but then I realized it would be more clear to use clean
directory structure and filenames with no prefix...
However I still think using prefix for variable and function names is
important as it greatly helps to debug :-)
For the time I could code we decided to talk on the list, so I have
switched to other tasks for now and wait to see Spen final changes to my
commits.. Again, I have put lots of work to make them clean and I think
they are ready, if you think otherwise I like to see the results of your
work ans then we will discuss the changes :-)
If you need additional explanations for my changes feel free to ask, I
worked on them lots of time and they seem obvious to me, but not
necessairyly for someone that can see them for the first time :-)
Best regards,
Tomek
--
CeDeROM, SQ7MHZ, http://www.tomek.cedro.info
25 sty 2013 03:45, "Peter Stuge" <[email protected]> napisał(a):
> CeDeROM wrote:
> > The goal should be the LOG script modification in a way that will
> > tell which file on which line produced a message and when...
>
> A fairly trivial change would be to make it output the function name.
> That information atom is easily searchable across the codebase, and
> is even slightly more future proof than a file:line specification
> which neccessarily changes across versions.
>
>
> > Regarding the file names it simply means that proper directory
> > structure is better than flat file list with prefix when the
> > directory structure represents code organization :-)
>
> Subdirectories can be good when used carefully, because they
> drastically reduce the overview at a glance.
>
>
> //Peter
>
>
> ------------------------------------------------------------------------------
> Master Visual Studio, SharePoint, SQL, ASP.NET, C# 2012, HTML5, CSS,
> MVC, Windows 8 Apps, JavaScript and much more. Keep your skills current
> with LearnDevNow - 3,200 step-by-step video tutorials by Microsoft
> MVPs and experts. ON SALE this month only -- learn more at:
> http://p.sf.net/sfu/learnnow-d2d
> _______________________________________________
> OpenOCD-devel mailing list
> [email protected]
> https://lists.sourceforge.net/lists/listinfo/openocd-devel
>
------------------------------------------------------------------------------
Master Visual Studio, SharePoint, SQL, ASP.NET, C# 2012, HTML5, CSS,
MVC, Windows 8 Apps, JavaScript and much more. Keep your skills current
with LearnDevNow - 3,200 step-by-step video tutorials by Microsoft
MVPs and experts. ON SALE this month only -- learn more at:
http://p.sf.net/sfu/learnnow-d2d
_______________________________________________
OpenOCD-devel mailing list
[email protected]
https://lists.sourceforge.net/lists/listinfo/openocd-devel
