reuse/web: web-based ada reuse in his article "software reuse myths" from the january 1988 issue of _acm sigsoft software engineering notes,_ will tracz discusses why software reuse has not grown to its full potential. engineers first proposed the concept of a subroutine library at the university of cambridge in 1949. yet the concept has not extended much past this level.at the time tracz wrote this article, interest had begun to reemerge in the concept of software reuse. still, tracz believes that nine myths surround software reuse that have prevented it from becoming more widespread. specifically, three myths relate to my thesis:1. software reuse is a technical problem.2. special tools are needed for software reuse.3. ada has solved the reuse problem.as far as the first myth goes, the only technical problem is the lack of search methods to find the right pieces of code (which my project should help alleviate). beyond that, the problem is more psychological, sociological or economic. for example, there is the "not from here" attitude pervading industry that icads people to believe that software developed outside of their company is unreliable.tracz believes you only need special tools (the second myth) when you become truly serious about reuse. most software libraries, he claims, are only 100-200 components in size and that programmers can easily navigate this many components without any tools. also, most instances of reuse occur when a programmer modifies existing programs that either he or a coworker wrote, so again he does not need a tool to find what he needs. i believe that the reuse mentality is a difficult one to accept and any tool that can make the transition to this attitude easier should be explored and utilized, no matter how small the number of components in the software library.tracz refutes the third myth by stating that "writing a generic package in ada does not necessarily make it reusable any more than writing a fortran subroutine or assembly language macro." simply put, generic packages are not enough to encourage reuse because the packages must still be instantiated with actual data types. the attitudes of the programmers using the language are more important than the language itself in determining whether or not code will be reused. i hope that my project makes ada more accessible to code reuse and can change some programmers' attitudes about reuse.i believe that this attitude can change if programmers have access to a simple tool to browse software libraries that runs on a variety of hardware platforms to maximize usage and potential. this idea gave rise to reuse-www, an ada specification file browser running under netscape. since netscape runs on many platforms (pc, macintosh, unix-based., etc.), an application using netscape as its "operating system" would be ideal. fortunately, recent developments in world wide web programming, such as javascript and perl cgi (common gateway interface) have made this goal extremely attainable.reuse-www may not run under microsoft's internet explorer, though. it also does not provide any editing, compiling, linking, or running capabilities. i assume that a potential user of the system already has an editor of choice and knows where to get an ada 95 compiler, such as gnat. john petren john beidler