Andrew M., what we would do? Would we make some changes in the test system?
(if yes - what kind of changes? Is it described in tickets on trac?)

 

 - Andrew

 

  _____  

From: [email protected] [mailto:[email protected]] On Behalf
Of Andrey Maslennikov
Sent: Tuesday, June 01, 2010 11:35 AM
To: [email protected]
Subject: Re: Meeting 31-05-2010 -- offline

 

About failed tests. Now test system doesn't support application parameters
and can't check them. It's the reason.

On Tue, Jun 1, 2010 at 11:31 AM, Букирев Андрей <[email protected]> wrote:

ping Maxim L. 

ping Fedor K.

ping Andrew M.

 

 - Andrew 

 

  _____  

From: [email protected] [mailto:[email protected]] On Behalf
Of Андрей Лапин
Sent: Monday, May 31, 2010 2:39 PM
To: [email protected]
Subject: Re: Meeting 31-05-2010 -- offline

 

"--strip*" keys

--strip-call all|file|line|param
--strip-def all|file|return|line|param
--strip-imp all|file|return|line|param
--strip-all

It would be more comfortable for my opinion.

But, on the other hand i have new idea!!  We can save all CallGraph but show
only part what need customer.
On this case, keys will be added in tools that will translate CallGraph to
text(so on). But it is really more difficult to implement i think and
moreover size of CallGraph will be stay huge (as i see we want to change
it).

So, i'm look forward to any comments.


2010/5/31 Букирев Андрей <[email protected]>

Hi, everybody!

 

I suggest to don't meet today and discuss all (as possible) in this email
thread.

 

Agenda:

*       Internationalization mechanism in SA

*       AB: I have implemented example with using gettext library on
Windows. Now I have just one bug with incorrect encoding in windows' console
(CP 866 - DOS instead of CP 1251). I'll 
*       send my example to sa_team afrer successful fix.
*       AB: Maxim L., what is status on Linux? Did you try to modify SA
build system to build SA with gettext? AR: Maxim L., Could you do and test
it on this week? 

*       Repo reconstruction

*       AB: I have done some replacements - see "sourceanalyzer-workflow"
repo. Rev 469 - 472
(http://bitbucket.org/sourceanalyzer/sourceanalyzer-workflow)
*       AB: If we'll have any other items on it - Yaroslav G. will implement
it. AR: Everybody, if you have add something - please email

*       Translation of wiki-pages and mans

*       AB: mans have been translated and uploaded to repo
(http://bitbucket.org/sourceanalyzer/sourceanalyzer-workflow/src/tip/docs/ru
ssian/). But I don't see it in action. Could somebody "build" this mans?
*       AB: You can see wiki-pages in on-line here:
http://trac-hg.assembla.com/SourceAnalyzer. I'll edit student translation
step-by-step. (AR: anybody can help if s/he want).

*       Parser of pointers to functions

*       AB: AR: Andrew L., please provide your status update.

*       SA as separate library

*       AB: AR: Fedor K., please provide your status update.

*       Failed tests

*       AB: Two failed tests (#11 - base.salink, #13 - base.saupdate)  AR:
Andrew M., could you make it clear where is problem and fix it?
*       AB: Failed tests in debug mode (if you use Microsoft compiler) AR:
Fedor K., Andrew L. Andrew B. discuss it and find solution for it.

*       Main.cpp for GAS parser

*       AB: Team, what happened? I have two version: 1. we should implement
main.cpp for Gas parser 2. we had main.cpp but fogot it somewhere. Thus, we
should find and restore it. What is true and what would we do? 

*       "--strip*" keys

*       AB: AR: Andrew L.: please provide your status update. What way did
you choose?

*       <Something else from you>

 

Best Regards,

 - Andrew

 

-- 
You received this message because you are subscribed to the Google Groups
"SourceAnalyzer Team" group.
To post to this group, send email to [email protected].
To unsubscribe from this group, send email to
[email protected]
<mailto:sa_team%[email protected]> .
For more options, visit this group at
http://groups.google.com/group/sa_team?hl=en.




-- 
Andrew Lapin

-- 
You received this message because you are subscribed to the Google Groups
"SourceAnalyzer Team" group.
To post to this group, send email to [email protected].
To unsubscribe from this group, send email to
[email protected]
<mailto:sa_team%[email protected]> .
For more options, visit this group at
http://groups.google.com/group/sa_team?hl=en.

-- 
You received this message because you are subscribed to the Google Groups
"SourceAnalyzer Team" group.
To post to this group, send email to [email protected].
To unsubscribe from this group, send email to
[email protected]
<mailto:sa_team%[email protected]> .
For more options, visit this group at
http://groups.google.com/group/sa_team?hl=en.




-- 
Best Regards,
Andrey

-- 
You received this message because you are subscribed to the Google Groups
"SourceAnalyzer Team" group.
To post to this group, send email to [email protected].
To unsubscribe from this group, send email to
[email protected].
For more options, visit this group at
http://groups.google.com/group/sa_team?hl=en.

-- 
You received this message because you are subscribed to the Google Groups 
"SourceAnalyzer Team" group.
To post to this group, send email to [email protected].
To unsubscribe from this group, send email to 
[email protected].
For more options, visit this group at 
http://groups.google.com/group/sa_team?hl=en.

Reply via email to