I'm having some trouble with my copy constructor. I've tried using gdb
to find the bug, but it seg faults in the destructor. I'm not able to
see what I'm doing wrong. Since I'm using pointers, I need deep copy
and I believe I'm doing that in my constructors. Can someone help me
see what I'm missing out? Here is my code.
typedef boost::shared_p tr<FactorFactor Ptr;
enum FactorTypeT
{ FACTOR_ZERO, FACTOR_ONE, FACTOR_AND, FACTOR_OR};
class Factor
{
private:
struct FactorImpl *fact;
Factor();
Factor(const FactorTypeT type, const int index,
const Factor *next, const Factor *same);
Factor(const Factor& rhs);
static FactorPtr convNodeToFacto r(const NodePtr& n, const NodePtr&
ntree);
static FactorPtr convNodeToFacto rRecur(const NodePtr& n, const
NodePtr& ntree);
public:
~Factor();
static FactorPtr create();
static FactorPtr create(const FactorPtr& rhs);
};
struct FactorImpl
{
FactorTypeT type;
int idx;
struct FactorImpl *nextlevel;
struct FactorImpl *samelevel;
FactorImpl()
: type(FACTOR_UNK NOWN), idx(-1), nextlevel(0), samelevel(0) {}
// copy constructor
FactorImpl(cons t FactorImpl& rhs)
{
*this = rhs;
}
~FactorImpl()
{
if (nextlevel)
delete nextlevel;
if (samelevel)
delete samelevel; <------------ it segfaults here
}
FactorImpl& operator=(const FactorImpl& rhs)
{
if (this != &rhs)
{
type = rhs.type;
idx = rhs.idx;
if (rhs.nextlevel)
nextlevel = new FactorImpl(*rhs .nextlevel); <--- deep copy
right?
if (rhs.samelevel)
samelevel = new FactorImpl(*rhs .samelevel); <-- deep copy
right?
}
return *this;
}
void dump(std::ostre am& f)
{
static std::string str[7] = {"-0-", "-1-", "AND", "OR", "???"};
f << this << " " << str[type] << " " << idx << "\n";
if (nextlevel)
nextlevel->dump(f);
if (samelevel)
samelevel->dump(f);
}
};
Factor::Factor( )
: fact(new FactorImpl()) {}
Factor::Factor( const FactorTypeT type, const int index,
const Factor *next, const Factor *same)
: fact(new FactorImpl())
{
fact->type = type;
fact->idx = index;
if (next)
fact->nextlevel = new FactorImpl(*nex t->fact); <----
making deep copy?
if (same)
fact->samelevel = new FactorImpl(*sam e->fact); <---- making
deep copy ?
}
Factor::~Factor ()
{
delete fact;
}
Factor::Factor( const Factor& rhs)
: fact(new FactorImpl())
{
*fact = *(rhs.fact);
}
FactorPtr Factor::create( )
{
FactorPtr f(new Factor());
return f;
}
FactorPtr Factor::create( const FactorPtr& rhs)
{
FactorPtr f(new Factor(*rhs));
return f;
}
FactorPtr Factor::convNod eToFactor(const NodePtr& n, const NodePtr&
ntree)
{
switch (ntree->getFunction( ))
{
case NODE_ZERO:
return FactorPtr(new Factor(FACTOR_Z ERO, -1, 0, 0));
case NODE_ONE:
return FactorPtr(new Factor(FACTOR_O NE, -1, 0, 0));
default:
return Factor::convNod eToFactorRecur( n, ntree);
}
}
FactorPtr Factor::convNod eToFactorRecur( const NodePtr& n, const
NodePtr& ntree)
{
if (ntree->getType() != NODE_UNASSIGNED )
return FactorPtr(new Factor(FACTOR_L EAF, n->faninIndex(ntr ee), 0,
0));
unsigned int j;
NodePtr fanin;
FactorPtr lit, tmp, gand, gor, curand, curor;
gor = curor = FactorPtr();
for (int i = ntree->numCubes() - 1; i >= 0; --i)
{
gand = curand = FactorPtr();
foreach_fanin(n tree, j, fanin)
{
switch (ntree->getLiteral(i , j))
{
case VZERO:
tmp = Factor::convNod eToFactorRecur( n, fanin);
lit = FactorPtr(new Factor(FACTOR_I NV, -1, 0, tmp.get()));
<------- this line causes a segfault. the problem is with pass
tmp.get() (which is a valid pointer to object) so I need to do a deep
copy. not sure if i'm doing deep copy correctly.
break;
case VONE:
lit = Factor::convNod eToFactorRecur( n, fanin);
break;
default:
break;
}
if (!curand)
gand = curand = lit;
else
{
curand->fact->samelevel = (lit.get())->fact;
curand = lit;
}
}
if (!gand)
bailOut("Factor ::convNodeToFac torRecur()",
ERROR_NODE_NOT_ MINIMALBASE_FUN CTION);
else if (!gand->fact->samelevel)
gand = FactorPtr(new Factor(FACTOR_A ND, -1, 0, gand.get()));
if (!gor)
gor = curor = gand;
else
{
curor->fact->samelevel = (gand.get())->fact;
curor = gand;
}
}
if (!gor)
bailOut("Factor ::convNodeToFac torRecur()",
ERROR_NODE_NOT_ MINIMALBASE_FUN CTION);
else if (!gor->fact->samelevel)
gor = FactorPtr(new Factor(FACTOR_O R, -1, 0, gor.get()));
return gor;
}
Program received signal EXC_BAD_ACCESS, Could not access memory.
Reason: KERN_INVALID_AD DRESS at address: 0xbf7ffffc
0x000b3b20 in FactorImpl::~Fa ctorImpl (this=0xd010c0) at factor.cpp:52
52 delete samelevel;
thanks for any help. 7 2164
pallav skrev:
I'm having some trouble with my copy constructor. I've tried using gdb
to find the bug, but it seg faults in the destructor. I'm not able to
see what I'm doing wrong. Since I'm using pointers, I need deep copy
and I believe I'm doing that in my constructors. Can someone help me
see what I'm missing out? Here is my code.
[snip]
It would be easier if the code was compilable/runnable.
--
OU
pallav wrote:
I'm having some trouble with my copy constructor. I've tried using gdb
to find the bug, but it seg faults in the destructor. I'm not able to
see what I'm doing wrong. Since I'm using pointers, I need deep copy
and I believe I'm doing that in my constructors. Can someone help me
see what I'm missing out? Here is my code.
typedef boost::shared_p tr<FactorFactor Ptr;
enum FactorTypeT
{ FACTOR_ZERO, FACTOR_ONE, FACTOR_AND, FACTOR_OR};
class Factor
{
private:
struct FactorImpl *fact;
Factor();
Factor(const FactorTypeT type, const int index,
Top-level const's are meaningless.
const Factor *next, const Factor *same);
Factor(const Factor& rhs);
static FactorPtr convNodeToFacto r(const NodePtr& n, const NodePtr&
What's "NodePtr"?
ntree);
static FactorPtr convNodeToFacto rRecur(const NodePtr& n, const
NodePtr& ntree);
public:
~Factor();
static FactorPtr create();
static FactorPtr create(const FactorPtr& rhs);
};
The "Rule of Three" is violated here.
[..]
Also, there is no need to verify that the pointer is non-null before
using 'delete' on it.
Also, you have memory leaks -- in the FactorImpl::ope rator= you don't
deallocate (delete) the pointers.
Also, using the assignment operator in the copy-constructor is counter-
intuitive. Using them the other way around might be OK...
See FAQ 5.8.
V
--
Please remove capital 'A's when replying by e-mail
I do not respond to top-posted replies, please don't ask
On May 1, 2:55 pm, pallav <pallavgu...@gm ail.comwrote:
I'm having some trouble with my copy constructor. I've tried using gdb
regarding the post above, i did some more investigating and have
narrowed the problem down to these two functions:
FactorImpl(cons t FactorImpl& rhs)
{
*this = rhs;
}
FactorImpl& operator=(const FactorImpl& rhs)
{
if (this != &rhs)
{
type = rhs.type;
idx = rhs.idx;
if (rhs.nextlevel)
nextlevel = new FactorImpl(*rhs .nextlevel);
if (rhs.samelevel)
samelevel = new FactorImpl(*rhs .samelevel);
}
return *this;
}
when the operator= is entered *this contains the following values
type = 13691
idx = 0
nextlevel = 0x0
samelevel = 0x3
so its an initalization problem. since rhs.samelevel = 0x0 samelevel
is never modified from the garbage values and hence the segfault.
if i understand correctly *this = rhs means call the constructor on
this and then do the =. correct? this means that FactorImpl() should
have been called on this and *this should be equal to
type = 0
idx = -1
nextlevel = 0x0
samelevel = 0x0
then the assignment would take place. is this not correct? i have to
copy the variable initializer list in operator=?
thanks
pallav wrote:
On May 1, 2:55 pm, pallav <pallavgu...@gm ail.comwrote:
>I'm having some trouble with my copy constructor. I've tried using gdb
regarding the post above, i did some more investigating and have
narrowed the problem down to these two functions:
FactorImpl(cons t FactorImpl& rhs)
{
Right here all the members in 'this' object contain garbage since you
don't initialise them.
*this = rhs;
}
FactorImpl& operator=(const FactorImpl& rhs)
{
if (this != &rhs)
{
type = rhs.type;
idx = rhs.idx;
if (rhs.nextlevel)
nextlevel = new FactorImpl(*rhs .nextlevel);
if (rhs.samelevel)
samelevel = new FactorImpl(*rhs .samelevel);
}
return *this;
}
when the operator= is entered *this contains the following values
type = 13691
idx = 0
nextlevel = 0x0
samelevel = 0x3
so its an initalization problem. since rhs.samelevel = 0x0 samelevel
is never modified from the garbage values and hence the segfault.
Yep.
if i understand correctly *this = rhs means call the constructor on
this
Huh?
and then do the =. correct? this means that FactorImpl() should
have been called on this and *this should be equal to
type = 0
idx = -1
nextlevel = 0x0
samelevel = 0x0
Huh?
>
then the assignment would take place. is this not correct? i have to
copy the variable initializer list in operator=?
Yes, I think that's the answer.
V
--
Please remove capital 'A's when replying by e-mail
I do not respond to top-posted replies, please don't ask
Hi,
Thanks for your time/help on this.
Top-level const's are meaningless.
const Factor *next, const Factor *same);
I'm not sure what you mean by this. You're saying it is not necessary
to make the arguments to constructors as const?
What's "NodePtr"?
It is typedef boost::shared_p tr<class NodeNodePtr;
The "Rule of Three" is violated here.
Here is what I have now. Is this correct way?
struct FactorImpl
{
FactorTypeT type;
int idx;
struct FactorImpl *nextlevel;
struct FactorImpl *samelevel;
FactorImpl()
: type(FACTOR_UNK NOWN), idx(-1), nextlevel(0), samelevel(0) {}
// copy
FactorImpl(cons t FactorImpl& rhs)
: type(rhs.type), idx(rhs.idx), nextlevel(0), samelevel(0)
{
if (rhs.nextlevel)
nextlevel = new FactorImpl(*rhs .nextlevel);
if (rhs.samelevel)
samelevel = new FactorImpl(*rhs .samelevel);
}
// destructor
~FactorImpl()
{
delete nextlevel;
delete samelevel;
}
// helper for assignment
void swap(FactorImpl & rhs)
{
std::swap(type, rhs.type);
std::swap(idx, rhs.idx);
std::swap(nextl evel, rhs.nextlevel);
std::swap(samel evel, rhs.samelevel);
}
// assignment
FactorImpl& operator=(const FactorImpl& rhs)
{
FactorImpl tmp(rhs);
tmp.swap(*this) ;
return *this;
}
};
class Factor
{
private:
struct FactorImpl *fact;
Factor();
Factor(const FactorTypeT type, const int index,
const Factor *next, const Factor *same);
Factor(const Factor& rhs);
Factor& operator=(const Factor& rhs);
void swap(Factor& rhs);
static FactorPtr convNodeToFacto r(const NodePtr& n, const NodePtr&
ntree);
static FactorPtr convNodeToFacto rRecur(const NodePtr& n, const
NodePtr& ntree);
public:
~Factor();
static FactorPtr create();
static FactorPtr create(const FactorPtr& rhs);
void dump(std::ostre am& f);
// I have a private ctor/assignment operator. I don't want the user
to be able to do assignment outside
// the class. Also I have done typedef boost::shared_p tr<Factor>
FactorPtr so the object is returned via a boost_shared ptr since it
will get attached to a node.
};
Factor::Factor( )
: fact(new FactorImpl()) {}
Factor::Factor( const FactorTypeT type, const int index,
const Factor *next, const Factor *same)
: fact(new FactorImpl())
{
fact->type = type;
fact->idx = index;
if (next)
fact->nextlevel = new FactorImpl(*nex t->fact);
if (same)
fact->samelevel = new FactorImpl(*sam e->fact);
}
Factor::~Factor ()
{
delete fact;
}
// copy constructor
Factor::Factor( const Factor& rhs)
: fact(new FactorImpl(*rhs .fact)) {}
// helper for assignment
void Factor::swap(Fa ctor& rhs)
{
std::swap(fact, rhs.fact);
}
// assignment operator
Factor& Factor::operato r=(const Factor& rhs)
{
Factor tmp(rhs);
tmp.swap(*this) ;
return *this;
}
// public static create functions
FactorPtr Factor::create( )
{
FactorPtr f(new Factor());
return f;
}
FactorPtr Factor::create( const FactorPtr& rhs)
{
FactorPtr f(new Factor(*rhs));
return f;
}
Also, there is no need to verify that the pointer is non-null before
using 'delete' on it.
Thanks for that.
Also, you have memory leaks -- in the FactorImpl::ope rator= you don't
deallocate (delete) the pointers.
Yes I see it now.
Also, using the assignment operator in the copy-constructor is counter-
intuitive. Using them the other way around might be OK...
I think i'll use the swap/copy constructor to implement the assignment
operator. The above code seems to work. Thanks for your time and help
again.
pallav wrote:
Thanks for your time/help on this.
Anytime.
>Top-level const's are meaningless.
>> const Factor *next, const Factor *same);
I'm not sure what you mean by this. You're saying it is not necessary
to make the arguments to constructors as const?
The ones you quoted here aren't the ones I referred to. These aren't
top-level. These are:
int foo(const int blah, const double blahblah);
>
>What's "NodePtr"?
It is typedef boost::shared_p tr<class NodeNodePtr;
You didn't mention it before. It was prohibiting us from compiling
your code. See FAQ 5.8.
>
>The "Rule of Three" is violated here.
Here is what I have now. Is this correct way?
I think I wrote that about Factor, not FactorImpl.
[..]
V
--
Please remove capital 'A's when replying by e-mail
I do not respond to top-posted replies, please don't ask
On May 1, 8:55 pm, pallav <pallavgu...@gm ail.comwrote:
I'm having some trouble with my copy constructor. I've tried using gdb
to find the bug, but it seg faults in the destructor. I'm not able to
see what I'm doing wrong. Since I'm using pointers, I need deep copy
and I believe I'm doing that in my constructors. Can someone help me
see what I'm missing out? Here is my code.
typedef boost::shared_p tr<FactorFactor Ptr;
enum FactorTypeT
{ FACTOR_ZERO, FACTOR_ONE, FACTOR_AND, FACTOR_OR};
class Factor
{
private:
struct FactorImpl *fact;
Factor();
Factor(const FactorTypeT type, const int index,
const Factor *next, const Factor *same);
Factor(const Factor& rhs);
static FactorPtr convNodeToFacto r(const NodePtr& n, const NodePtr&
ntree);
static FactorPtr convNodeToFacto rRecur(const NodePtr& n, const
NodePtr& ntree);
public:
~Factor();
static FactorPtr create();
static FactorPtr create(const FactorPtr& rhs);
};
struct FactorImpl
{
FactorTypeT type;
int idx;
struct FactorImpl *nextlevel;
struct FactorImpl *samelevel;
FactorImpl()
: type(FACTOR_UNK NOWN), idx(-1), nextlevel(0), samelevel(0) {}
// copy constructor
FactorImpl(cons t FactorImpl& rhs)
{
*this = rhs;
This line cannot work. You cannot, in general, implement copy
construction in terms of assignment, since copy construction
supposes that the left hand argument is fully constructed.
There are several ways around this, to avoid duplicating code;
in your case, just adding the initializer list from the default
constructor would work. However...
}
~FactorImpl()
{
if (nextlevel)
delete nextlevel;
if (samelevel)
delete samelevel; <------------ it segfaults here
You don't need the tests for NULL.
}
FactorImpl& operator=(const FactorImpl& rhs)
{
if (this != &rhs)
Red flag. If you have to test for self assignment, you're
usually doing something wrong...
{
type = rhs.type;
idx = rhs.idx;
if (rhs.nextlevel)
nextlevel = new FactorImpl(*rhs .nextlevel); <--- deep copy
right?
First, you're leaking memory. What happens to what nextlevel
pointed to before. You need a delete nextlevel here. But also,
what happens if there is an exception here or in the treatment
of samelevel? You end up with an object in a very strange
state.
The basic principle is right, but you're doing it in the wrong
place.
if (rhs.samelevel)
samelevel = new FactorImpl(*rhs .samelevel); <-- deep copy
right?
}
return *this;
}
This class seems to just scream for the swap idiom:
FactorImpl::Fac torImpl(
FactorImpl const& other )
: type( other.type )
, idx( other.idx )
, nextlevel( other.nextlevel == NULL
? NULL
: new FactorImpl( *other.nextleve l ) )
, samelevel( other.samelevel == NULL
? NULL
: new FactorImpl( *other.sameleve l ) )
{
}
FactorImpl&
FactorImpl::ope rator=(
FactorImpl const& other )
{
FactorImpl tmp( other ) ;
swap( tmp ) ;
return *this ;
}
void
FactorImpl::swa p(
FactorImpl& other )
{
std::swap( type, other.type ) ;
std::swap( idx, other.idx ) ;
std::swap( nextlevel, other.nextlevel ) ;
std::swap( samelevel, other.samelevel ) ;
}
Except that I'm not really sure that you even want to support
assignment. If this is the standard compilation firewall idiom,
you don't need assignment in the implementation class, you use
the swap idiom to implement assignment in the outer class.
void dump(std::ostre am& f)
{
static std::string str[7] = {"-0-", "-1-", "AND", "OR", "???"};
f << this << " " << str[type] << " " << idx << "\n";
if (nextlevel)
nextlevel->dump(f);
if (samelevel)
samelevel->dump(f);
}
};
Factor::Factor( )
: fact(new FactorImpl()) {}
Factor::Factor( const FactorTypeT type, const int index,
const Factor *next, const Factor *same)
: fact(new FactorImpl())
{
fact->type = type;
fact->idx = index;
if (next)
fact->nextlevel = new FactorImpl(*nex t->fact); <----
making deep copy?
if (same)
fact->samelevel = new FactorImpl(*sam e->fact); <---- making
deep copy ?
}
Factor::~Factor ()
{
delete fact;
}
Factor::Factor( const Factor& rhs)
: fact(new FactorImpl())
{
*fact = *(rhs.fact);
}
Why not simply:
Factor::Factor(
Factor const& other )
: fact( new FactorImpl( *other.fact ) )
{
}
IMHO, you're doing far too much with assignment. Get copy
construction right, without assignment, and then use the swap
idiom, or something similar, for assignment. (Factor is so
simple, even the swap idiom seems like overkill:
Factor&
Factor::operato r=(
Factor const& other )
{
FactorImpl* tmp = new FactorImpl( *other.fact ) ;
delete fact ;
fact = tmp ;
return *this ;
}
FactorPtr Factor::create( )
{
FactorPtr f(new Factor());
return f;
}
FactorPtr Factor::create( const FactorPtr& rhs)
{
FactorPtr f(new Factor(*rhs));
return f;
}
FactorPtr Factor::convNod eToFactor(const NodePtr& n, const NodePtr&
ntree)
Since you've not shown us anything concerning the nodes, I can't
really comment on the rest. But in general, for recursive
structures like this, the rule is to do the recursion in the
copy constructor (and the destructor, obviously), and for
assignments, use the copy constructors to create a new instance
of the recursive structure, then either delete the old instance,
and assign the new, or---if the new instance is in a fully
formed object with an adequate destructor, to play pointer games
(swap) so that the current instance ends up with the new, and
the temporary with the old; the destructor of the temporary
object will then take care of the deletes, when we leave the
operator=.
--
James Kanze (GABI Software) email:ja******* **@gmail.com
Conseils en informatique orientée objet/
Beratung in objektorientier ter Datenverarbeitu ng
9 place Sémard, 78210 St.-Cyr-l'École, France, +33 (0)1 30 23 00 34 This thread has been closed and replies have been disabled. Please start a new discussion. Similar topics |
by: A |
last post by:
Hi,
A default copy constructor is created for you when you don't specify one
yourself. In such case, the default copy constructor will simply do a
bitwise copy for primitives (including pointers) and for objects types call
their default constructor.
Any others points i should know?
|
by: Christian Engström |
last post by:
When i compile the program listed below with gcc version 3.3.1 (MinGW on
Windows XP) I get the following result:
Calling 'func(d)':
'base' copy constructor
Calling 'func(*d_handle)':
'base' copy constructor
Calling 'func(d_handle)':
|
by: August1 |
last post by:
This is a short program that I have written from a text that
demonstrates a class object variable created on the stack memory and
another class object variable created on the heap memory. By way of
the text, the program is supposed to demonstrate the use of a copy
constructor function for the object created on the heap (because there
is a char* pointer variable in the instantiated class) and how you
would use the delete keyword with the...
|
by: August1 |
last post by:
I've written an interface and implementation file along with a client
source file that allows the use of an overloaded subtraction operator.
However, when
using the program, I'm running into a memory problem that I'm not
readily seeing that lies within the overloaded operator - I think
pertaining to the temporary class object that is created and used to
return a value of the operands and the pointer variable of the class.
Could someone...
|
by: Ashwin |
last post by:
hi guys,
i have overloaded the << operator.as shown below.
ostream& operator<<(ostream &out, const student &a)
{
out<<a.idno;
out<< " " ;
// out<< a.name;
out<< " " ;
// out<< a.marks << endl;
| |
by: Brian |
last post by:
Dear Programmers,
I have a class with a pointer to an array. In the destructor, I just
freed this pointer. A problem happens if I define a reference to a
vector of this kind of class. The destruction of the assigned memory
seems to call the class destructor more than once. I don't know the
reason or whether I used the vector class correctly. Attached is my
program. Thanks for your help.
Regards,
|
by: xqxu.pzhou |
last post by:
I wrote a simple allocator "myAlloc" under the g++ 3.2.3. When it is
used by Vector, it works well. But when it is used by List, the codes
have errors when compling. the error message is:
"no matching function for call to myAlloc<std::_List_node<int>
Then I added the following copy constructor to "myAlloc", now it works
well.
"template <typename U>
myAlloc(const myAlloc<U>&) {}"
|
by: campos |
last post by:
Here are my codes:
#include <iostream>
using namespace std;
class Test
{
public:
Test() { cout << "Test()" << endl; }
|
by: dragoncoder |
last post by:
Hello experts,
I have the following code me.
=cat mystring.h
#include<iostream>
using namespace std;
class mystring
{
|
by: Jeroen |
last post by:
Hi all,
I'm trying to implement a certain class but I have problems regarding
the copy ctor. I'll try to explain this as good as possible and show
what I tried thusfar. Because it's not about a certain code syntax but
more a 'code architecture' thing , I'll use simple example classes
(which are certainly not complete or working...) just to illustrate the
idea (and I may make some mistakes because I'm not that experienced...).
The...
|
by: marktang |
last post by:
ONU (Optical Network Unit) is one of the key components for providing high-speed Internet services. Its primary function is to act as an endpoint device located at the user's premises. However, people are often confused as to whether an ONU can Work As a Router. In this blog post, we’ll explore What is ONU, What Is Router, ONU & Router’s main usage, and What is the difference between ONU and Router. Let’s take a closer look !
Part I. Meaning of...
| |
by: Oralloy |
last post by:
Hello folks,
I am unable to find appropriate documentation on the type promotion of bit-fields when using the generalised comparison operator "<=>".
The problem is that using the GNU compilers, it seems that the internal comparison operator "<=>" tries to promote arguments from unsigned to signed.
This is as boiled down as I can make it.
Here is my compilation command:
g++-12 -std=c++20 -Wnarrowing bit_field.cpp
Here is the code in...
|
by: Hystou |
last post by:
Overview:
Windows 11 and 10 have less user interface control over operating system update behaviour than previous versions of Windows. In Windows 11 and 10, there is no way to turn off the Windows Update option using the Control Panel or Settings app; it automatically checks for updates and installs any it finds, whether you like it or not. For most users, this new feature is actually very convenient. If you want to control the update process,...
|
by: tracyyun |
last post by:
Dear forum friends,
With the development of smart home technology, a variety of wireless communication protocols have appeared on the market, such as Zigbee, Z-Wave, Wi-Fi, Bluetooth, etc. Each protocol has its own unique characteristics and advantages, but as a user who is planning to build a smart home system, I am a bit confused by the choice of these technologies. I'm particularly interested in Zigbee because I've heard it does some...
|
by: isladogs |
last post by:
The next Access Europe User Group meeting will be on Wednesday 1 May 2024 starting at 18:00 UK time (6PM UTC+1) and finishing by 19:30 (7.30PM).
In this session, we are pleased to welcome a new presenter, Adolph Dupré who will be discussing some powerful techniques for using class modules.
He will explain when you may want to use classes instead of User Defined Types (UDT). For example, to manage the data in unbound forms.
Adolph will...
|
by: conductexam |
last post by:
I have .net C# application in which I am extracting data from word file and save it in database particularly. To store word all data as it is I am converting the whole word file firstly in HTML and then checking html paragraph one by one.
At the time of converting from word file to html my equations which are in the word document file was convert into image.
Globals.ThisAddIn.Application.ActiveDocument.Select();...
|
by: TSSRALBI |
last post by:
Hello
I'm a network technician in training and I need your help.
I am currently learning how to create and manage the different types of VPNs and I have a question about LAN-to-LAN VPNs.
The last exercise I practiced was to create a LAN-to-LAN VPN between two Pfsense firewalls, by using IPSEC protocols.
I succeeded, with both firewalls in the same network. But I'm wondering if it's possible to do the same thing, with 2 Pfsense firewalls...
| |
by: 6302768590 |
last post by:
Hai team
i want code for transfer the data from one system to another through IP address by using C# our system has to for every 5mins then we have to update the data what the data is updated we have to send another system
|
by: muto222 |
last post by:
How can i add a mobile payment intergratation into php mysql website.
| |