Files
harbour-core/harbour/contrib/hbtpathy
Przemyslaw Czerpak 1cc8e1e88c 2013-01-10 23:25 UTC+0100 Przemyslaw Czerpak (druzus/at/poczta.onet.pl)
* harbour/include/hbapicls.h
  * harbour/src/vm/classes.c
    + added new internal C function:
         void hb_objCloneTo( PHB_ITEM pDest, PHB_ITEM pSource,
                             PHB_NESTED_CLONED pClonedList );
      it copies object or clone it if class overloaded clone operation.
    ; TODO: add support for user defined class clone operation

  * harbour/include/hbapiitm.h
  * harbour/src/vm/itemapi.c
    * changed returned type of hb_itemCloneTo() to void

  * harbour/src/vm/itemapi.c
    * use hb_objCloneTo() in hb_itemClone*() functions.

  * harbour/src/vm/arrays.c
    * use hb_objCloneTo() in array/hash clone code.

  * harbour/src/vm/arrayshb.c
    ! fixed return values in AEVAL() and ACOPY() when array
      is passed by reference.

  * harbour/src/rtl/tclass.prg
  * harbour/src/vm/classes.c
    * declare :SUPER and :__SUPER messages as non virtual ones.
      Now ::SUPER and ::__SUPER messages executed in object method
      returns casting to 1-st super object of the class in which
      executed method was defined.

  * harbour/include/hbclass.ch
    * removed xtranslations for SUPER(): - this workaround for
      missing non virtual messages in some Clipper OOP implementations
      was breaking valid code which tried to use real :SUPER message
      and made SUPER reserved word, i.e. it was not possible to create
      code like:
         LOCAL super := ::parent2
         ? super:v1, super:v2
      Now this hack is not longer necessary and :SUPER is non virtual
      massage in Harbour.
      INCOMPATIBLE: If someone has some code like:
         SUPER():MSG()
         SUPER( PARENT ):MSG()
      then please change it to:
         ::SUPER:MSG()
         ::PARENT:MSG()

  * harbour/contrib/hbmysql/tmysql.prg
  * harbour/contrib/hbmysql/tsqlbrw.prg
    ! fixed to use ::super() instead of super()

  * harbour/src/rdd/usrrdd/rdds/arrayrdd.prg
    + added GOCOLD() method - this method is necessary for WAs
      passed to HB_DBDETACH()

  * harbour/doc/xhb-diff.txt
    * small update

  * harbour/contrib/*/*.hbx
    * regenerated
2013-01-10 22:27:11 +00:00
..

/*
 * $Id$
 */

Telepathy is the best serial communication library for Nantucket/CA-Cl*pper.
I ported a significant amount of the functionality contained in Telepathy in
this Flagship port.

The .prg (in the MyTelepathy.tar package) is meant to be compiled with
Flagship and provide some of the functionality of the Telepathy serial
library from Extrasensory Inc.  I've talked to Ira Emus, the proprietor of
Extrasensory and he's ok with what I've done here.  But Extrasensory has no
involvement or responsibility with this project.

I wrote this originally on RedHat Linux 5.1 and I've tested it on RedHat
6.2.  And now Neolinux 2.0.1 and 2.1.  I've tested it on kernels 2.0.x - 2.4.x.
Your mileage may vary.

I only ported the parts of Telepathy that I needed.  If you need other parts
of the telepathy libarary, Use the Source... (and send me your new functions)

I tried to keep parameter counts and orders as consistent as possible between
this Telepathy and the real Telepathy.  The only difference I can think of is
the parameter list for tp_open (and tp_reopen).  That's just because unix has
filename comports like /dev/ttyS0 and dos has com port numbers like 1.  I kept
the com port number thing so that all the telepathy functions (and all your
code) that uses com port number won't need to be changed.  But you do need to
change the calls to tp_open.

Feel free to use, modify, distribute, hack, kludge, append, extend or whatever
you like to this source code.  You can (at your own risk) compile it into any
program you wish and sell or freely distribute the resulting application.  I
would prefer you make your application Free and distribute the source.  But who
am I to say - the suite of applications that my company sells that I originally
wrote this for is closed source.

Though I use this code in a production environment for a suite of programs that
my company actually sells, I make no promises (expressed or implied) about its
stability, functionality, effectiveness or anything else.  I warn you now
that if you use my code, you're doing so at your own risk and it will probably
blow up your computer.  But that's a risk you'll just have to take.

There is NO warranty; not even for MERCHANTABILITY or FITNESS FOR A PARTICULAR
PURPOSE (thanks RMS).
This software is totally as is, you may use it at your own risk.

This is freeware.  But if you actually use this in your program, please send
me email at dan@boba-fett.net.  I'd just be curious to see if anyone ever
uses it.

If you find a bug or write some new code for this project, pretty please send
me email with it.

- Dan Levitt <dan@boba-fett.net>