使用Moose进行代码库分析
[英]Progress codebase analysis using Moose
1 个解决方案
解决方案1
1 2014-01-01 21:05:03
From building a Delphi parser for Moose I know that it takes quite a lot of effort to get your FAMIX model complete. 
通过为Moose构建Delphi解析器，我知道完成FAMIX模型需要花费很多精力。 I'd recommend to make your feedback cycle as short as possible. 我建议您的反馈周期尽可能短。 From the progress grammar I'd say the system looks a bit more complicated than Delphi. 从进度语法上来说，我认为系统看起来比Delphi复杂。 Focus on the real & perceived problems and take shortcuts to find solutions for them. 着重于实际问题和感知问题，并采取捷径找到解决方案。 So you might want to delay writing a parser in Smalltalk, and just start using the pro parse stuff to generate a MSE file containing the interesting bits. 因此，您可能希望延迟在Smalltalk中编写解析器，而只是开始使用专业解析内容来生成包含有趣位的MSE文件。
If the system is really large you might have to be careful not to run out of memory currently. 如果系统确实很大，则可能必须小心不要当前耗尽内存。
You are aware of the humane assessment site ? 您知道人道评估网站吗？ The blog provides lots of examples and things to do/don't. 该博客提供了许多示例和不建议做的事情。
It really is an environment for developers, extremely powerful and having still a lot of rough edges. 对于开发人员而言，这确实是一个环境，它的功能极为强大，并且仍然存在很多困难。 The mailing list is very helpful 邮件列表非常有帮助
When dealing with legacy systems, there are a few things I do before starting Moose, to get a feeling for the system. 在处理遗留系统时，在开始Moose之前我需要做一些事情，以使您对系统有所了解。 I run a duplication detector and zip the individual table dumps (that works well on progress files). 我运行重复检测器并压缩各个表转储（在进度文件上运行良好）。 Large files that compress extremely well are interesting discussion topics :) 压缩效果非常好的大文件是有趣的讨论主题:)
声明:本站的技术帖子网页，遵循CC BY-SA 4.0协议，如果您需要转载，请注明本站网址或者原文地址。任何问题请咨询:yoyou2525@163.com.