Google Groups no longer supports new Usenet posts or subscriptions. Historical content remains viewable.
Dismiss

[VO27] - The Visual Objects Repository Code

4 views
Skip to first unread message

ilias

unread,
Aug 17, 2003, 12:55:38 PM8/17/03
to
source: http://www.grafxsoft.com/vo27.htm

-

>As VO developers know, much of Visual Objects is written in Visual Objects.

ok

>This was another area, that drastically need attention.

Taking in account that "{VO26 has tens of thousands of errors}" [1],
every application created with VO26 "drastically needs attention".

>All of the code that makes up your Visual Objects 2.7 Repository
>has been cleaned up, and run thought the Visual Objects
>compiler at the highest warnings.

Major library-code-cleanups can critically influence stability of
existing applications (problems when migrating VO26-sources to VO27).

There are already [possibly unnecessary] problems when migrating
VO25-sources to VO26.

>Many potential bugs we discovered in the course of doing this.

A warning is not an error.

A potential bug is not an error.

Correcting potential bugs is critical to the system-behaviour,
especially if the intention of the original-developers is unknown.

One example: a compiler-warning can be raised at a point, where the
core-developer does some tricky (and possibly undocumented)
workaround.

>As a result of this exercise new tools for development had to
>be written.

I don't understand this.

The Task: correct potential(!) bugs which are reported due to a higher
compiler warning-level setting.

Why there is a need for tools?

Assuming support- and refactoring-classes: I don't think that a few
support-classes or refactoring-classes are worth to be noted as tools.

>The result of these tools, you now will have the code that makes
>up your system repository delivered to you on the same CD as
>the product itself.

Again i don't understand.

The Task: Publishing the Source-Code on which the repository is based.

Why there is a need for tools?

Or is this 'tool' a simple batch-file, which extracts and copies the
public parts of the source-codes to a folder?

>No more, Repo & SDK out of sync.

Very nice.

'Transforming' to commonly known wording:

Repo => means here: Libraries
SDK => means here: Source-Code (of Libraries)
out-of-sync => means here: wrong version of source-code included

So we got this simple sentence:

=> The libraries included with VO27 will come with correct
source-code.

And this is of course a... totally obvious basic 'feature'.

-

[Background information: The libraries included with VO26 came with
source-code, too. For the bad luck of the developers which came in
touch with this source-codes: they have the wrong version ("Repo & SDK
out of sync").]

-
-

[1] - {VO26 has tens of thousands of errors}

source: [VO27] - Has been completely re-compiled in Microsoft Visual
Studio 7.1
http://groups.google.com/groups?selm=4fnsjv0p726cajstb4ns91j6nufsd9bg38%404ax.com

trollwatcher

unread,
Aug 18, 2003, 2:38:53 AM8/18/03
to
Toll Alert!
Do not fead the troll!
0 new messages