On Thu, 28 Feb 2002, Piroumian, Konstantin wrote:

> > On Thu, 28 Feb 2002, TREGAN Fabien wrote:
> >
> > > >BTW - what does "2mo" and "20ko" actually mean?
> > > >I can guess the meaning, but I've never seen it before.
> > > >And Google didn't find a quick answer for me ...
> > >
> > > Binary Digit (aka 'bit') is a number that can have to values (0 or 1)
> > > An Octet is 8 bits
> > > 1ko (kilo-octet) is 1024 bits (not 1000 because computer work with bit
> and
> > > then work with powre of 2, not power of 10)
> > > 1mo (mega-octet) is 1024 ko
> > >
> > > if your .java file is encoded in ascii, 1 octet = 1 char (space en
> > > cariage-return count as 1 char :) )
> > >
> > > So you can gues that finding a bug hidden in 20ko of code is 100 times
> > > shorted than finding it in 2mo of code.
> >
> > Well, I think this statement is kinda missleading. It is not the case
> > that your JVM only says "Hey there is an error, go find it somewhere!".
> > It will tell you either with a stack trace or by symptom to narrow the
> > problem area in the code.
>
> So what about logical errors? Your program can run perfectly, but perform
> not as you've been expecting. This is the case when 20K source code is
> easier to debug than 2M.
>
> If there will be a logical error in Avalon code which affects Cocoon then
> it'll be much more difficult to track it down.

Sure, but the statement was: "an error in a 20ko program can be found
100 times faster than in a 2mo program" which IMO is missleading.

Giacomo

>
> Konstantin
>
> >
> > Giacomo
> >
> > >
> > >
> > > >All articles on cocooncenter are written in xdoc (with some additions
> to
> > > fit the needs of my pages). So, if you wrote your tutorial in xdoc, it
> would
> > > be easy to publish.
> > >
> > > Since now, all my docs have been written in .doc (ms word), but i'll try
> to
> > > read the docs about how to write xdocs :)
> > >
> > > ---------------------------------------------------------------------
> > > To unsubscribe, e-mail: [EMAIL PROTECTED]
> > > For additional commands, email: [EMAIL PROTECTED]
> > >
> > >
> > >
> > >
> >
> >
> > ---------------------------------------------------------------------
> > To unsubscribe, e-mail: [EMAIL PROTECTED]
> > For additional commands, email: [EMAIL PROTECTED]
> >
>
> ---------------------------------------------------------------------
> To unsubscribe, e-mail: [EMAIL PROTECTED]
> For additional commands, email: [EMAIL PROTECTED]
>
>
>
>


---------------------------------------------------------------------
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, email: [EMAIL PROTECTED]

Reply via email to