Please see the Thread in the Xbase++ gui NG concerning this new Xbase++
feature.  I have documented some anomalies with this class, including one
scenario that result in a Fatal Error - I attached the Log.

BTW, how do you want such problems reported?

Alaska-software NG, Alaska-Research, eMail using form "pdrx.txt", etc?

-Joe

Joe,
This is a "undocumented" feature. Obviously there is a reason for this. 
It does not yet work!!!

Jim


Joe Carrick wrote:
> Please see the Thread in the Xbase++ gui NG concerning this new Xbase++
> feature.  I have documented some anomalies with this class, including one
> scenario that result in a Fatal Error - I attached the Log.
> 
> BTW, how do you want such problems reported?
> 
> Alaska-software NG, Alaska-Research, eMail using form "pdrx.txt", etc?
> 
> -Joe
> 
>

Hi James,

So much wasted time and memory space!  Why put a feature/capability into the
runtime if it doesn't work.  I would think these things could be commented
out - or kept in separate source code until ready.  This idea of creating
functionality and then just leaving it in the code but not documenting
because it's incomplete is ridiculous.

Perhaps if the code was open source so that the userbase could fix/enhance
it would be OK, but to just leave it in the runtime to take up space is
not OK.

-Joe

"James Loughner" <jwrl@charter.net> wrote in message
news:cgu9C1jzDHA.3332@S15147418...
> Joe,
> This is a "undocumented" feature. Obviously there is a reason for this.
> It does not yet work!!!
>
> Jim
>
>
> Joe Carrick wrote:
> > Please see the Thread in the Xbase++ gui NG concerning this new Xbase++
> > feature.  I have documented some anomalies with this class, including
one
> > scenario that result in a Fatal Error - I attached the Log.
> >
> > BTW, how do you want such problems reported?
> >
> > Alaska-software NG, Alaska-Research, eMail using form "pdrx.txt", etc?
> >
> > -Joe
> >
> >
>

Joe Carrick wrote:

> So much wasted time and memory space!  Why put a feature/capability into the
> runtime if it doesn't work.

If it isn't documented, it is not there 

Most likely it is more hassle to maintain two separate versions tha to
simply leave the code in there.

I'm quite sure that this is not the only "dead" code in the runtime...

> Perhaps if the code was open source so that the userbase could fix/enhance
> it would be OK, but to just leave it in the runtime to take up space is
> not OK.

With about 120 MB of my own DLL and EXE files, the few KB don't count 

Thomas

Xbase++ FAQ : www.software-braun.de/xbfaq/xbfaq.htm
A rock pile ceases to be a rock pile the moment a single man
contemplates it, bearing within him the image of a cathedral.
                -- Antoine de Saint-Exupery

Thomas Braun wrote:

> I'm quite sure that this is not the only "dead" code in the runtime...
> 

Depends how you define dead.
We often have things in the runtime from which we are not
shure yet how to work with. Or things that are precondition
for things to come. These things can then be used inhouse
with the same runtime that is deployed to our customers.
When bugs occur then, it is most likely that they occur to us.
(Call it "eat your own s***" if you like)

On the other hand, our support sometimes was able to
help at a very special issue. Then we lift the "secret" a 
little bit. But this is in a very special case then and
allways at the users risk.

Regards


Andreas Herdt


//////////////////////////////////////////////////////////////////
//
// Alaska Research & Development
// Homepage: www.alaska-research.com
// Newsgroup: nntp://news.alaska-Software.net
//
//////////////////////////////////////////////////////////////////

Andreas Herdt wrote:

>> I'm quite sure that this is not the only "dead" code in the runtime...
>>
>
> Depends how you define dead.

Thats why I put the "" around the word 

> On the other hand, our support sometimes was able to
> help at a very special issue. Then we lift the "secret" a
> little bit. But this is in a very special case then and
> allways at the users risk.

Oh yes, I can recall Frank++ telling this several times...

Thomas

Xbase++ FAQ : www.software-braun.de/xbfaq/xbfaq.htm
Actual newspaper headline: Red Tape Holds Up New Bridge

Joe
If i remember correctly XbpQuickEditBrowse is there at least from 1.7 version. It's not documented because it's not ready, and it's
not the only one. DACxxx is another one and you can find a lot more undocumented feautures.

Regards
Mike Evans

"Joe Carrick" <joe.carrick@dslextreme.com> wrote in message news:LshvVtjzDHA.3332@S15147418...
> Please see the Thread in the Xbase++ gui NG concerning this new Xbase++
> feature.  I have documented some anomalies with this class, including one
> scenario that result in a Fatal Error - I attached the Log.
>
> BTW, how do you want such problems reported?
>
> Alaska-software NG, Alaska-Research, eMail using form "pdrx.txt", etc?
>
> -Joe
>
>