Thoughts on VC++ bug fixing

delphi

    Next

  • 1. A Pirate's Life for Me! was Teamwork
    In borland.public.delphi.non-technical, Derek Davidson < XXXX@XXXXX.COM > wrote in message <400ffeaf$1 @newsgroups.borland.com>... > Don't you both think that this may be the teensiest bit off-topic? Ahoy maties! We's got another ship to plunder. Shiver me timbers. Make haste to Britannia, and throw away the wenches. We won't needs them where we is going! [followups set to off-topic] -- ***Free Your Mind***
  • 2. OMG, another feature request ;) - addendum
    (work for compiler) if a class has not such ("override") OnFail routine, but has new data fields, compiler should issue appropriate warning. those checkings are optional, of course, with "safe class" option.
  • 3. Delphi 8 books/tutorials?
    Any books/tutorials on D8 in the works? I just installed it, and find it bewildering. Haven't a clue how or where to start. Exactly as I felt when firing up my first D. Help was, then, absolutely worthless -- for the rank beginner. A bit like trying to learn to fly by reading a manual on the technical specs of the engine. I assume Help in D8 will be no better, so I haven't even looked at it yet (but will do so after posting this message). I expect to learn D8 like I did my first D, from a few books that will take my hand and guide me through some baby steps, then on to the point where I can begin to navigate on my own. I looked over Marco Cantu's web site, hoping to see an upcoming "Mastering Delphi 8". I realize it's a bit early for that, but saw no indication that one might be planned. In the meantime, what's a good place to start, at gound-zero? Ideal would be a little tutorial -- on the web or in the first chapter of a book -- that took the approach: ok, children, follow me along, step-by-step, as we build this simple web app..... Thanks, Ben Crain
  • 4. Upgrade necessary?
    Aside from .NET capabilities, is there any other compelling reason to upgrade from version 7 (i.e. core language changes, marked improvements in the IDE, etc.)? Thanks. Zach
  • 5. Delphi 8 in Argentina
    Arrived yesterday.

Thoughts on VC++ bug fixing

Postby Delphi Guy » Wed, 07 Jun 2006 00:22:34 GMT

Please see:
">>Microsoft has made it pretty clear not only to me but even to MVPs that
VC++ is not a product where bugs are going to be fixed in the next release.
<<"
 http://www.**--****.com/ 

Also especially the 2nd user's comment:
"Intellisense is a nightmare, the property pane outdated (__gc ????) and the
IDE crashes every 5 minutes.

I've VS2005 installed for a while but continue to use VC6, maybe we should
ask for a refund."

Is it just me, or does this sound what users used to say about Delphi? :)

Maybe VS2005 is not so great after all, especially users who always
criticise delphi and say they moving to VS,
maybe the grass is not always greener on the other side, so one must always
first see what's happening the other
side of the fence before they jump ship.
Better the devil you know, than the devil you don't :)



Re: Thoughts on VC++ bug fixing

Postby Alan Garny » Wed, 07 Jun 2006 00:35:57 GMT





Personally, I don't care so much about the other side. If I was to compare, 
I would rather compare with what Borland used to produce.

In my case, I cannot explain to myself my experience with BDS2006. When I 
got my copy, I installed it (together with GExperts, some components of mine 
as well as some from JCL/JVCL and, later, Delphi Speedup) and it was working 
relatively fine. There would be the occasional irk (which I hate), but 
nothing that would, in all fairness, prevent me from working normally.

Then, a month ago or so, I reinstalled Windows XP and, in the process, 
BDS2006. There is no difference in the way I installed BDS2006, yet, 
whenever I want to close BDS2006 (with only the Win32 personality loaded) it 
will generate lots of exception. The only way to actually close BDS2006 is 
via the Task Manager (!!). I uninstalled Delphi Speedup as it is a 
relatively recent piece of software, but to no avail. As for everything else 
(i.e. GExperts, some components of mine as well as some from JCL/JVCL, they 
worked fine with D7 and my first installation of BDS2006, so I don't think 
that could be the problem), I don't think it's the cause, but who knows?!

So, at the moment, I am rather annoyed with BDS2006 not closing properly. 
There is also the occasional case where the Search feature just doesn't want 
to work (quite a few QC entries are related to it in fact).

    Alan. 



Re: Thoughts on VC++ bug fixing

Postby Jim Dodd » Wed, 07 Jun 2006 01:04:14 GMT



You probably did this but just in case - Did you also install all the
updates to Windows XP after reinstalling? How about the update for
BDS2006?

I've had to reinstall Windows (various flavors) over the years and I'm
always amazed how much extra work I have to do to AFTER the reinstall to
get everything working again.

Good luck,
Jim Dodd
Onset Computer Corp.

Re: Thoughts on VC++ bug fixing

Postby Alan Garny » Wed, 07 Jun 2006 02:59:38 GMT







I always install all updates of all the softwares I have on my computer, so 
yes both Windows XP and BDS2006 are up to date.


Do you mean installing the updates or do some special tricks?

    Alan. 



Re: Thoughts on VC++ bug fixing

Postby Ingvar Anderberg » Wed, 07 Jun 2006 04:15:21 GMT

"Alan Garny" < XXXX@XXXXX.COM > skrev 


Don't know about BDS 2006 but when reinstalling Delphi 2005
you have to start the IDE at least once before installing the updates,

/ia


Re: Thoughts on VC++ bug fixing

Postby Alan Garny » Wed, 07 Jun 2006 14:42:28 GMT





Well, I believe I did, but just in case, I have, yet again, reinstalled 
BDS2006 and made sure that I started it before installing update #2. Will 
see how it goes...

    Alan 



Re: Thoughts on VC++ bug fixing

Postby Jim Dodd » Wed, 07 Jun 2006 22:44:28 GMT







I meant installing all the updates (Windows and applications), setting 
up preferences (Windows and applications) and reinstalling all the 
Delphi/BCB components we use. This was just a comment and I'm sure you 
know what you need to do for this. It's just that there are SO MANY 
things to do after a reinstall, it is easy to miss something. Or do them 
out of order!

I love Delphi and BCB but the richness of the environment is also a 
draw-back. You have to reproduce the programming environment nearly 
exactly (there's got to be a better way to say that :-) in order to work 
on another machine or after a reinstall. And that can take a long time.

Regards,
Jim Dodd
Onset Computer Corp.

Re: Thoughts on VC++ bug fixing

Postby Jim Dodd » Wed, 07 Jun 2006 22:56:29 GMT






 >> I've had to reinstall Windows (various flavors) over the years and I'm
 >> always amazed how much extra work I have to do to AFTER the reinstall to
 >> get everything working again.
 >
 > Do you mean installing the updates or do some special tricks?
 >
 >     Alan.
 >

I meant installing all the updates (Windows and applications), setting
up preferences (Windows and applications) and reinstalling all the
Delphi/BCB components we use. This was just a comment and I'm sure you
know what you need to do for this. It's just that there are SO MANY
things to do after a reinstall, it is easy to miss something. Or do them
out of order!

I love Delphi and BCB but the richness of the environment is also a
draw-back. You have to reproduce the programming environment nearly
exactly (there's got to be a better way to say that :-) in order to work
on another machine or after a reinstall. And that can take a long time.

Regards,
Jim Dodd
Onset Computer Corp.

Re: Thoughts on VC++ bug fixing

Postby Mike Margerum » Sun, 11 Jun 2006 02:53:09 GMT

ive been using vstudio 2005 for about 6 months now doing native c++ and 
C# apps and I don't think it has ever crashed on me.  The code 
completion still sucks for C++ though.




Similar Threads:

1.List of some of the bugs fixed bugs in DeXter

2.Fix VC++/Borland libpq build - pqsignal

3.problem using delphi dll in vc++

hi,
I am using a delphi DLL in vc++,static linked with ".h"and "lib".
the export functions in DLL are "__stdcall",but the function doesn't
work well,it often returns some weird values.
when I add codes as follows,it suddenly works well. why??

         DWORD returnAdd;
         __asm
         {
               mov ecx,[ebp+4]
               mov returnAdd, ecx
         }

 I am confused,if there is something wrong with stack,I have already
using "__stdcall",why it is still wrong?
I don't even know what those asm code do,I just add them to get some
status about stack.what else they do to the program that I don't know?

thank you .
Ryan

4.porting from 16 bit Borland c to 32 vc++ (emergency)

hi

this is an emergency and i need to know wat wud be the sizes of various 
stuctures wriiten in 16 bit borland c (c++ i think).  i need to read the 
files of the old version software and i have read most of the objects stored 
but some still need help.

struct OldMultiBuffer {
	unsigned unused:3;		// Unused flags
	unsigned isCeiling:1;		// Object is on the ceiling
	int x0,y0,z0;		// 3D reference point
	RECT topBounds;		// Plan view bounds
	int unused2[2];		// Unused space
	int height;			// Height of bottom of obj
	BYTE unused3[28];		// Unused space
	void *unused4;		// Meaningless pointer
	int rotatedAngle;
	int thisWallHeight;
};

this is one struct i need to know the sizeof.

Another is a piece of code which i need to know how much it reads so i can 
skip the part. it is storing a bitmap.

file.get((PARENT*) this+1,sizeof *this-sizeof(PARENT)-sizeof hDib);

the PARENT is:

struct far Obj: public ObjBase
{
	HOBJ group;	// Owning group or NULL
	HOBJ hNext;	// Next object in group or NULL
	HOBJ hPrev;	// Previous object in group or NULL

	enum Type {	// Object type
		Group,	// (00) Group of objects
		Text,	// (01) Text
		Line,	// (02) Line
		Conline,	// (03) Constrained line
		Rect,	// (04) Rectangle
		RoundRect,// (05) Rounded Rectangle
		Ellipse,	// (06) Ellipse
		Arc,	// (07) Arc
		Poly,	// (08) Polygon
		Sketch,	// (09) Freehand sketch
		Chart,	// (0A) Chart
		Bitmap,	// (0B) Clip art
		Slice,	// (0C) Pie slice
		Chord,	// (0D) Chord of ellipse
		DimLine,	// (0E) Dimension line
		Wall,	// (0F) Wall
		Multi,	// (10) Multiview object
		HollowLine,// (11) Hollow line
		Stud,	// (12) Studs
		Horizon,	// (13) Horizon line
	} type;
	WORD obView;	// Object view
	WORD obLayer;	// Object layer

	struct far Flags {
		unsigned isLocked:1;	// Object is currently locked
		unsigned isHidden:1;	// Object is currently not visible
		unsigned canAltSelect:1;// Object has alternate select mode
		unsigned isSelected:1;// Object is currently selected
		unsigned isAltSelected:1;// Object in alternate select mode
		unsigned isPartial:1;	// Object is being edited
		unsigned isGroup:1;	// Class is (derived from) GroupObj
		unsigned boundsDirty:1;// Object bounds must be recalculated
		unsigned isEstimable:1;// Include in estimator export
		unsigned isMaterial:1;	// Include in materials list
		unsigned cantFlip:1;	// Object is reflectively retarded
		unsigned cantRotate:1;// Object is rotationally retarded
		unsigned reserved2:4;// Future use

		Flags (void) { *(LPWORD) this=0; }
		operator WORD (void) const { return *LPWORD(this); }
		void operator = (WORD w) { *LPWORD(this)=w; }
	} flags;

	char szdescribe1[20];		// Object character description
	char szdescribe2[20];		// Estimating text field
	char szUnit[3];		// Estimating unit field
	int nObjID;			// Identification number
	WORD magnifyX;		// Horz magnification in 1024ths
	WORD magnifyY;		// Vert magnification in 1024ths
	WORD nDataIndex1;		// Plant number in plant database
	int nAge;			// Age for plants, -1 if N/A
	RECT workBounds;		// Cached bounds rectangle

	int height;			// Height of wall; height of other
				//   objs off ground; ignored for					//   Multi-view objs on ceiling

	static BOOL bReadingOldMigFile;	// From pre-ObjReadBuffer days
	static POINT hitPoint;
	static char scratch[80];

	Obj(Type);			// Constructor
	virtual ~Obj (void);		// Destructor
	static Obj *read (InFile&);	// Read object from input file

	Obj *next (void);		// Get next object in group
	Obj *prev (void);		// Get previous object in group
	virtual void select (void);	// Select object for editing
	void unselect (void);		// Unselect object

	virtual RECT getBoundsRect (void)=0; // Get logical bounds
	virtual RECT getUpdateRect (void);// Get drawing bounds
	virtual RECT getHandleRect (void);// Get sizing handle rect
	virtual WORD describe (void);	// Return description string ID
	virtual int getRotatedAngle (void);// Get angle object has rotated
	virtual int getObjHeight (void);	// Return object height off ground
	virtual int getObjWidth (void);	// Return width (x) and length (y) of
	virtual int getObjLength (void);	//   object in logical units
	virtual long getObjArea (void);	// Return area in square logical units
	virtual long getObjLinearfeet (void);// Get linear ft if applicable
	virtual LPSTR getObjAngle (void);// Get angle from vertical
				//	 (not rotated angle)

	virtual BOOL hit (RECT*)=0;	// Test hit by rectangle
	virtual TextObj *hitText (RECT*);// Test hit on editable text
	virtual Handle *getHitHandle (POINT);  // Test hit on handle
	virtual void outline (void);	// Draw object outline
	virtual void draw (BOOL grayed=FALSE);// Draw complete object
	virtual void drawHandles (void);	// Draw object handles
	virtual void moveHandle (Handle*,POINT);  // Move handle of object
	virtual void unMoveHandle (HaMemo*);// Undo handle movement
	virtual void releaseHandle (Handle*);// End handle movement
	virtual void doChange (Change*); // Apply attribute change
	virtual void unChange (Change::Type,ChMemo*);  // Unapply attribute change
	virtual void reChange (Change::Type,ChMemo*);  // Reapply attribute change
	virtual void apply (Xform&)=0;	// Apply coordinate xform
	virtual void unApply (XfMemo*);	// Unapply coordinate xform
	virtual void reApply (XfMemo*);	// Reapply coordinate xform
	virtual void devChange (void);	// Adjust to new device or res
	virtual void setScale (WORD,WORD);  // Change drawing-to-world scale
	virtual void prep (void);	// Prepare to write to file
	virtual void put (OutFile&);	// Write object to file
	virtual Obj* getDeleteObj (void);	// Get underlying obj to delete
	virtual InfoDlg *getInfoDlg (void);	// Return properties dialog

	int getDescription (LPSTR,int);
	LPSTR getObjLayer (void);	// Return layer object is in

  protected:
	virtual int enumHandles (BOOL f(int,int));	// Enumerate handles
	static BOOL drawHandle (int,int);	// Draw one object handle
	static BOOL hitHandle (int,int);	// Test hit on handle
	static int enumCorners (RECT*,BOOL f(int,int));
};


and below is this:

struct BitmapObj: public Obj {
	RECT pos;		// Location, not normalized
	POINT size;	// Bitmap size in pixels
	int accuHandle;	// Handle to Accusoft bitmap
	HGLOBAL hDib;	// Handle to the DIB
};

i think this is reading 14 bytes but i am not sure since on some files it 
seem to work but not on all.

5.problem using delphi dll in vc++

hi,
I am using a delphi DLL in vc++,static linked with ".h"and "lib".
the export functions in DLL are "__stdcall",but the function doesn't
work well,it often returns some weird values.
when I add codes as follows,it suddenly works well. why??

         DWORD returnAdd;
         __asm
         {
               mov ecx,[ebp+4]
               mov returnAdd, ecx
         }

 I am confused,if there is something wrong with stack,I have already
using "__stdcall",why it is still wrong?
I don't even know what those asm code do,I just add them to get some
status about stack.what else they do to the program that I don't know?

thank you .
Ryan



Return to delphi

 

Who is online

Users browsing this forum: No registered users and 35 guest