Re: Release of RosAsm V.2.025a

Guga wrote:
> The only sad thing on your statements Randall is that you are the one
> who don=B4t know what you are talking about, and, by consequence, you
> are spreading lies again.
>
> Example:
>
> "And resolving things like conflicting names, merging duplicate code,
> and all those other things that plague this type of "monolithic"
> software development. The really sad thing is that the RosAsm team
> really doesn't know any better. "
>
> Just a lie .. Duplicated symbols or functions when merged the user is
> warned because it won =B4t assemble the file due to the duplications.
> The error management is exactlyto prevent this sort of things.

You really do not understand why namespace pollution is a bad thing, do
you?
Then again, this should come as no surprise from a user of the
assembler that encourages people to use label names like I0, I1, I2,
I3, etc.

>
> > The RosAsm team doesnt understand what a "team project" is all about.
"
>
> Maybe you didn=B4t read what i posted or you just disconsidered on your
> attacks on rene...but..on all you posted you really seems clueless on
> what it is all about, the clip features, the incinclude statements
> preparsers and the lib scanners.

How many professional developers, whose day jobs include work on large
software systems (tens to hundreds of programmers) are involved with
the development of RosAsm? I thought so. Does the phrase "the blind
leading the blind" mean anything to you? I'm sure, in your state of
ignorance, you think that what you're doing is "team programming." The
truth is, you only think this because you don't know any better. Those
who've actually done some *real* software engineering in their
lifetimes are laughing at you behind your backs.

>
>> "They *really, really* don't understand how team project management
>> should be done."
>
> So, pls enlight us with your "universal" knowledge.

Pick up any decent book on software engineering and team project
management. Read it. Practice what it preaches. You will quickly
discover *much* better ways of doing team projects. And you'll quickly
discover that RosAsm is somewhat under-featured for such a task.

>
> If that means disseminating arrogancy or flames on our team of
> co-workers...Sorry..this won=B4t happen :)

You're already doing that. Rene's approach of "I'm not providing
libraries because I want to force people to code the way I do" is a
perfect example of such arrogance. If you weren't forcing people to
work the way *you* wanted them too, you'd provide the static linking
capability and let *them* choose how to write their code.

>
> A team work using different files and people thinking together of the
> whole project is what a team work is based on. The way it is developed
> is not different from other techniques of working in team you want to
> impose...

You've got it backwards. RosAsm's current development scheme is the one
*forcing* things onto people. Forcing naming conventions for separate
components (which wouldn't be necessary if you sup****ted static linking
with file-scope naming). Think about it. How would allowing people to
work on modules as separate object files *force* your users to do
something they're doing now? Heck, if they *wanted* to do the
monolithic thing, they *still* could. It's your current scheme that
adds the restrictions that force people to work a certain way.
Cheers,
Randy Hyde