Re: Release of RosAsm V.2.025a

Betov wrote:
> >
> > Why don't you answer the questions? This is the occasion to prove the
> > superiority of the clip technology!
>
> Because there is nothing to be answered:

IOW, the clip system is in no way shape or form superior to statically
linked library modules.

>
>
> > And other questions : How do you do concurrent work on a project with
> > RosAsm if the project is one file?
>
> We depress [Ctrl]/[S] for saving the concerned TITLE, and
> exchange the .asm File. For Resources exchanges, we also
> have special Binary Formats, and all of these make the
> exchanges as simple as a Click.

IOW, it's all manual. The RosAsm team has no clue about modern software
engineering techniques and how to manage team projects.

>
>
> > Do you use a file revision system?
>
> Of course not.

:-)

>
>
> > Do you merge modifications by hand by copying blocks in the main
RosAsm
> > version?
>
> Of course not.

He's lying. Of course they do. He just doesn't understand what you're
asking.

>
>
> > Do you have to wait somebody has finished working to begin modifying
the
> > project?
>
> Our rule is quite simple: Once a volunteer has been attributed
> a TITLE, _he_, and only _he_ is allowed to touch _his_ TITLE.

See the statement above.
Yep. The RosAsm scheme truly sup****ts team projects :-) :-) :-)


>
> In other words, we never have two volunteers writing the same
> TITLE at the same time,

The RosAsm team doesnt understand what a "team project" is all about.


> and when two volunteers "work around"
> a same TITLE (for example, actualy, Guga and me working both
> at a time on the LibScanner), there is one doing one task
> (example, searching for the Doc, preparing the developements,
> controling the progresses,...), while the other one really
> _writes_ the TITLE.


They *really* don't understand what team project management is all
about.

>
> When two volunteers really want to work (_write_) on the
> same component, we divide the TITLE into two TITLEs.

They *really, really* don't understand how team project management
should be done.


> Example,
> recently Ludwig, who is in charge of the Debugger, wrote
> something for the Assembler... in a _separated_ TITLE.

It's really a completely separate project. Subject, of course, to the
limitations that it cannot reuse label and variable names from the
*other* separate applications that are merged into RosAsm. Such are the
benefits of the "monolithic source file format" that RosAsm forces on
its users.


>
> When finished, merging two TITLEs is just a matter of
> deleting one Statement in the Source.

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.

>
>
> > I really suspect that multiple files is mandatory when working with a
> > large team on the same project.
>
> Up to now, whatever number of volunteers working directly on
> some part of RosAsm, we never had any problem, with the actual
> methods, and, in my opinion, even though RosAsm has the most
> im****tant Team of Developpers for an Assembly Project, we could
> even be 10 times more volunteers, that it would not make any
> difference.

HaHaHa!
The leader of the RosAsm team demonstrates his software engineering
competence with this last statement!
Cheers,
Randy Hyde