From d54893b18ec81b10a8b690b4402cba6e7f042204 Mon Sep 17 00:00:00 2001
From: Marty Kraimer
Date: Tue, 10 Aug 2010 13:23:17 -0400
Subject: [PATCH] modify test. update README
---
README.html | 41 ++++++++---------------------------------
pvDataApp/test/test.cpp | 5 +++++
2 files changed, 13 insertions(+), 33 deletions(-)
diff --git a/README.html b/README.html
index e83279b..29015a0 100644
--- a/README.html
+++ b/README.html
@@ -10,7 +10,7 @@
EPICS pvData C++
Overview
-2010.08.02
+2010.08.10
CONTENTS
@@ -27,26 +27,9 @@ following is done:
Scalar
test
A test of Scalar.
- As mentioned below there are major problems with the current
+ As mentioned below there are problems with the current
implementation.
-
-Since the last version the following are the main changes:
-
Building
@@ -76,14 +59,14 @@ type:
The pure virtual classes defined in pvData.h now work. But there are still
some things that are not so nice. Amoung these are:
- - User code sees pointers instead of references. Can this be changed
- while keeping the boost::shared_ptr support?
+ - In FieldCreateFactory.cpp look for "WHY DO I". It asks why the derived
+ class must also define methods defined in the base class. If it does not
+ then a compilation error occurs. WHY???
- The toString methods have an argument of "std::string &buf" instead
- of "std::string *". But in the test code I could not create a
- "std::string &" to work. I do not know why.
+ of "std::string *". Does this seem correct?
- Can arguments and return descriptions be defined better?
- Is const present everywhere it should be? Remember that introspection
- classes are immutable and are shared whereever possible.
+ classes are immutable.
- The code is NOT thread safe. When we decide for sure what thread/lock
support to choose I will fix this.
@@ -94,14 +77,6 @@ with c++
Garbage Collection
-
-boost::shared_ptr is currenly used for implementations of Field, Scalar,
-etc. It is also used for all string arguments passed to methods. Since string
-values are freely shared by pvData, pvAccess, etc, this is really important.
-questions:
-
- - Is the implementation using shared_ptr correctly?
- - Should other things currently defined use stared_ptr?
-
+Not yet implemented. Lets get class structure correct first.