home *** CD-ROM | disk | FTP | other *** search
- Release 1.1.1 notes.
-
- This release fixes several memory leaks in the TDate and TDateField functions.
- Care should be taken when calling TDate::formatDate because it allocate newStr
- storage for the pointer it returns. Using a call like: sprintf( buf, "The date
- is: %s", mydate.formatDate(MDY) ) will cause a memory leak since the string
- storage is never deleted. Instead use a call like: sprintf( buf, "The date is:
- %s", char *temp = mydate.formatDate(MDY) ); delete(temp); this should avoid the
- problem. I'm considering implementing another format function to return a
- pointer to a static string storage area. Any comments on this are welcomed.
-
- Thanks to Elliott Jackson (CIS 72311,3616) for his recommendations fixing a
- potential memory leak in the TDate + and - operators.
-
- Several people pointed out a bug in the TField classes when several routines
- set the terminating null on the data string with code like the
- following: data[maxLen + 1] = EOS; This has been corrected to read:
- data[maxLen] = EOS. This may still look like a bug to some, but remember data
- was initialized as data[aMaxLen] and maxLen was initialized to aMaxLen - 1.
- The maxLen data item stored internal to a TField DOES NOT include the
- terminating NULL, where the aMaxLen value passed to the constructor DOES
- include the terminating NULL. I have corrected the documentation re: aMaxLen
- in TField's constructor to correctly state this fact. Thanks to everyone who
- pointed this out.
-
- This release includes two new TField derivatives: TLowerField and TDoubleField
- (tlwfield.cpp and tdbfield.cpp respectively in the ZIP). These were submitted
- by Jerry Jankura (CIS 70170,306) Thanks for the help Jerry! I've also added
- a TLongDoubleField (tldfield.cpp) class.
-
- This release also fixes a problem with the TIntField/TLongField/TFloatField
- min/max validation which incorrectly worded the warning messages. Thanks to
- Ernest Rowland for pointing this out.
-
- If you have any TField derivatives from which you think others could benefit, or
- if you have any comments or suggestions regarding this effort, please let me
- know.
-
- Files included in TFIELD.ZIP are:
- README.TFD -- this file
- TFIELD.DOC -- ascii documentation file (incomplete version)
- TFIELDDC.WP5 -- WP51 documentation file (incomplete version)
- TFIELD.H -- header file for the classes
- TDATE.CPP -- TDate class routines
- TFIELD.CPP -- TField class routines
- TDFIELD.CPP -- TDateField class routines
- TFFIELD.CPP -- TFloatField class routines
- TIFIELD.CPP -- TIntField class routines
- TLFIELD.CPP -- TLongField class routines
- TUFIELD.CPP -- TUpperField class routines (Uppercase version of TField)
- TFLDEX.CPP -- Example file to demonstrate the classes
- TFLDEX.PRJ -- Project file for BC++ 3.0 to build the example under IDE
- TLWFIELD.CPP -- TLowerField class routines
- TLDFIELD.CPP -- TLongDoubleField class routines
- TDBFIELD.CPP -- TDoubleField class routines
- TFLDLIB.BAT -- Creates a TFIELD.LIB, assumes all .OBJ files exist
- TFLDLIB.RSP -- Response file used to build TFIELD.LIB
-
- MBB
-
-
- Release 1.1 notes.
-
- This version was developed and tested under BC++ 3.0. You're welcome to
- try to get it to run under BC++ 2.0, but I won't attempt to support it on
- that platform!
-
- The tfield.doc file is incomplete, but looking at my schedule it could be
- another week or more before I can get it finished, so I'm releasing it as-
- is for now. It should be complete enough to allow you to get by. It anyone
- feels like helping, I'm including the Word Perfect 5.1 file, feel free to
- edit it if you want <g>.
-
- Special thanks to Steve Marcus, Eric Simon and Chris Hill for their work on
- developing the DATECL.ZIP Date class, from which I derived TDate.
-
- This version has not had much performance tuning, yet. It does, however, run
- adequately fast on a 486/33 <g> (though trying to use the IDE debugger in some
- routines is still terribly slow!) I don't think performance should suffer much
- on anything less than a 286/12. I could be wrong, however.
-
- If you find any bugs, or have any ideas or suggestions for improving this
- class, please let me know via CIS mail and/or post a message on S11 of the
- BPROGB forum, I try to monitor there frequently enough to catch all messages,
- though I may be a few days in responding.
-
- I hope that you find these useful!
-
- Michael Bonner
- CIS: 73250,1460
-