I have a class called 'PrimaryKey' that represents the primary key of a
table.
PrimaryKeys can only be created and the class only implements .ToString().
The PrimaryKey class internally stores the data as either a int or a Guid
depending on the structure of the database.
If we simply used int to represent a primary key, rather than this
PrimaryKey class then programmers could do things like performing
mathematically operations on the primary key which should be best avoided
since this is not the nature of primary keys.
The PrimaryKey class works really well except when it comes to exposing it
through SOAP. Because the class contains no public fields and no public
properties then SOAP/WSDL does not expose any insights into the class.
When an instance of the PrimaryKey class flows through SOAP and turns up at
the client I can't actually do anything with it since I can't get any data
out of it and cast it into the client's PrimaryKey class.
Ideally I would to put an attribute around the 'private int primaryKey'
field of the PrimaryKey class (that internally records the value of the
primary key) so that it can be exposed to SOAP and SOAP alone.
Is this possible? I have studied the SOAP attributes and nothing seems
available. Are there any work arounds?
One idea I had was to drop the .ToString() method and just have a .Value
property. I would only implement the Get and not the Set but evidently
SOAP/WSDL needs both a Get and a Set before it is exposed to SOAP.
Thanks in advance
Dave A
8  1863 
I'm afraid there's no simple and easy answer to this issue. As you've
noticed, the XML serializer serializes only public fields and read-write
properties. The data format is customizable to some extent, but all private
state and behavior associated with your classes is lost.
That said, it is possible to hack around this issue. You can edit the
consumer-side proxy, remove the data classes generated along with the proxy
and have the proxy refer to the original class(es). This does allow you to
share the same type between the web service and the consumer and thus share
behavior, but private state is still lost.
The bottom line is that if you really want to share objects between a
service and its consumers, then you might want to consider using a
distributed object technology such as .NET Remoting. Web Services merely
pass XML documents back and forth, and trying to share types or behavior
will run into issues.
Regards,
Sami
"Dave A" <da**@sigmasolutionsdonotspamme.com.au> wrote in message
news:Oo****************@TK2MSFTNGP10.phx.gbl... I have a class called 'PrimaryKey' that represents the primary key of a
table.
PrimaryKeys can only be created and the class only implements .ToString().
The PrimaryKey class internally stores the data as either a int or a Guid
depending on the structure of the database.
If we simply used int to represent a primary key, rather than this
PrimaryKey class then programmers could do things like performing
mathematically operations on the primary key which should be best avoided
since this is not the nature of primary keys.
The PrimaryKey class works really well except when it comes to exposing it
through SOAP. Because the class contains no public fields and no public
properties then SOAP/WSDL does not expose any insights into the class.
When an instance of the PrimaryKey class flows through SOAP and turns up
at the client I can't actually do anything with it since I can't get any
data out of it and cast it into the client's PrimaryKey class.
Ideally I would to put an attribute around the 'private int primaryKey'
field of the PrimaryKey class (that internally records the value of the
primary key) so that it can be exposed to SOAP and SOAP alone.
Is this possible? I have studied the SOAP attributes and nothing seems
available. Are there any work arounds?
One idea I had was to drop the .ToString() method and just have a .Value
property. I would only implement the Get and not the Set but evidently
SOAP/WSDL needs both a Get and a Set before it is exposed to SOAP.
Thanks in advance
Dave A
I'm afraid there's no simple and easy answer to this issue. As you've
noticed, the XML serializer serializes only public fields and read-write
properties. The data format is customizable to some extent, but all private
state and behavior associated with your classes is lost.
That said, it is possible to hack around this issue. You can edit the
consumer-side proxy, remove the data classes generated along with the proxy
and have the proxy refer to the original class(es). This does allow you to
share the same type between the web service and the consumer and thus share
behavior, but private state is still lost.
The bottom line is that if you really want to share objects between a
service and its consumers, then you might want to consider using a
distributed object technology such as .NET Remoting. Web Services merely
pass XML documents back and forth, and trying to share types or behavior
will run into issues.
Regards,
Sami
"Dave A" <da**@sigmasolutionsdonotspamme.com.au> wrote in message
news:Oo****************@TK2MSFTNGP10.phx.gbl... I have a class called 'PrimaryKey' that represents the primary key of a
table.
PrimaryKeys can only be created and the class only implements .ToString().
The PrimaryKey class internally stores the data as either a int or a Guid
depending on the structure of the database.
If we simply used int to represent a primary key, rather than this
PrimaryKey class then programmers could do things like performing
mathematically operations on the primary key which should be best avoided
since this is not the nature of primary keys.
The PrimaryKey class works really well except when it comes to exposing it
through SOAP. Because the class contains no public fields and no public
properties then SOAP/WSDL does not expose any insights into the class.
When an instance of the PrimaryKey class flows through SOAP and turns up
at the client I can't actually do anything with it since I can't get any
data out of it and cast it into the client's PrimaryKey class.
Ideally I would to put an attribute around the 'private int primaryKey'
field of the PrimaryKey class (that internally records the value of the
primary key) so that it can be exposed to SOAP and SOAP alone.
Is this possible? I have studied the SOAP attributes and nothing seems
available. Are there any work arounds?
One idea I had was to drop the .ToString() method and just have a .Value
property. I would only implement the Get and not the Set but evidently
SOAP/WSDL needs both a Get and a Set before it is exposed to SOAP.
Thanks in advance
Dave A
Thanks. I appreciate the effort that you put into that great answer.
There has to be a solution though. I am going to keep thinking about it and
if I come up with something then I will post back what I find.
"Sami Vaaraniemi" <sa**********@pleasejippii.fi> wrote in message
news:eL**************@TK2MSFTNGP09.phx.gbl... I'm afraid there's no simple and easy answer to this issue. As you've
noticed, the XML serializer serializes only public fields and read-write
properties. The data format is customizable to some extent, but all
private state and behavior associated with your classes is lost.
That said, it is possible to hack around this issue. You can edit the
consumer-side proxy, remove the data classes generated along with the
proxy and have the proxy refer to the original class(es). This does allow
you to share the same type between the web service and the consumer and
thus share behavior, but private state is still lost.
The bottom line is that if you really want to share objects between a
service and its consumers, then you might want to consider using a
distributed object technology such as .NET Remoting. Web Services merely
pass XML documents back and forth, and trying to share types or behavior
will run into issues.
Regards,
Sami
"Dave A" <da**@sigmasolutionsdonotspamme.com.au> wrote in message
news:Oo****************@TK2MSFTNGP10.phx.gbl...I have a class called 'PrimaryKey' that represents the primary key of a
table.
PrimaryKeys can only be created and the class only implements
.ToString().
The PrimaryKey class internally stores the data as either a int or a Guid
depending on the structure of the database.
If we simply used int to represent a primary key, rather than this
PrimaryKey class then programmers could do things like performing
mathematically operations on the primary key which should be best avoided
since this is not the nature of primary keys.
The PrimaryKey class works really well except when it comes to exposing
it
through SOAP. Because the class contains no public fields and no public
properties then SOAP/WSDL does not expose any insights into the class.
When an instance of the PrimaryKey class flows through SOAP and turns up
at the client I can't actually do anything with it since I can't get any
data out of it and cast it into the client's PrimaryKey class.
Ideally I would to put an attribute around the 'private int primaryKey'
field of the PrimaryKey class (that internally records the value of the
primary key) so that it can be exposed to SOAP and SOAP alone.
Is this possible? I have studied the SOAP attributes and nothing seems
available. Are there any work arounds?
One idea I had was to drop the .ToString() method and just have a .Value
property. I would only implement the Get and not the Set but evidently
SOAP/WSDL needs both a Get and a Set before it is exposed to SOAP.
Thanks in advance
Dave A
Thanks. I appreciate the effort that you put into that great answer.
There has to be a solution though. I am going to keep thinking about it and
if I come up with something then I will post back what I find.
"Sami Vaaraniemi" <sa**********@pleasejippii.fi> wrote in message
news:eL**************@TK2MSFTNGP09.phx.gbl... I'm afraid there's no simple and easy answer to this issue. As you've
noticed, the XML serializer serializes only public fields and read-write
properties. The data format is customizable to some extent, but all
private state and behavior associated with your classes is lost.
That said, it is possible to hack around this issue. You can edit the
consumer-side proxy, remove the data classes generated along with the
proxy and have the proxy refer to the original class(es). This does allow
you to share the same type between the web service and the consumer and
thus share behavior, but private state is still lost.
The bottom line is that if you really want to share objects between a
service and its consumers, then you might want to consider using a
distributed object technology such as .NET Remoting. Web Services merely
pass XML documents back and forth, and trying to share types or behavior
will run into issues.
Regards,
Sami
"Dave A" <da**@sigmasolutionsdonotspamme.com.au> wrote in message
news:Oo****************@TK2MSFTNGP10.phx.gbl...I have a class called 'PrimaryKey' that represents the primary key of a
table.
PrimaryKeys can only be created and the class only implements
.ToString().
The PrimaryKey class internally stores the data as either a int or a Guid
depending on the structure of the database.
If we simply used int to represent a primary key, rather than this
PrimaryKey class then programmers could do things like performing
mathematically operations on the primary key which should be best avoided
since this is not the nature of primary keys.
The PrimaryKey class works really well except when it comes to exposing
it
through SOAP. Because the class contains no public fields and no public
properties then SOAP/WSDL does not expose any insights into the class.
When an instance of the PrimaryKey class flows through SOAP and turns up
at the client I can't actually do anything with it since I can't get any
data out of it and cast it into the client's PrimaryKey class.
Ideally I would to put an attribute around the 'private int primaryKey'
field of the PrimaryKey class (that internally records the value of the
primary key) so that it can be exposed to SOAP and SOAP alone.
Is this possible? I have studied the SOAP attributes and nothing seems
available. Are there any work arounds?
One idea I had was to drop the .ToString() method and just have a .Value
property. I would only implement the Get and not the Set but evidently
SOAP/WSDL needs both a Get and a Set before it is exposed to SOAP.
Thanks in advance
Dave A
I knew there had to be an answer and there is!
It just barely works with .NET 1.x - http://dotnetified.com/PermaLink.asp...F-CDA36ACF481F
And it fully works with .NET
2.0 -http://weblogs.asp.net/cweyer/archive/2004/08/02/205798.aspx
Dave A
('Exposing private members using SOAP and XML Serialization' - that is there
for google)
"Dave A" <da**@sigmasolutionsdonotspamme.com.au> wrote in message
news:%2****************@TK2MSFTNGP10.phx.gbl... Thanks. I appreciate the effort that you put into that great answer.
There has to be a solution though. I am going to keep thinking about it
and if I come up with something then I will post back what I find.
"Sami Vaaraniemi" <sa**********@pleasejippii.fi> wrote in message
news:eL**************@TK2MSFTNGP09.phx.gbl... I'm afraid there's no simple and easy answer to this issue. As you've
noticed, the XML serializer serializes only public fields and read-write
properties. The data format is customizable to some extent, but all
private state and behavior associated with your classes is lost.
That said, it is possible to hack around this issue. You can edit the
consumer-side proxy, remove the data classes generated along with the
proxy and have the proxy refer to the original class(es). This does allow
you to share the same type between the web service and the consumer and
thus share behavior, but private state is still lost.
The bottom line is that if you really want to share objects between a
service and its consumers, then you might want to consider using a
distributed object technology such as .NET Remoting. Web Services merely
pass XML documents back and forth, and trying to share types or behavior
will run into issues.
Regards,
Sami
"Dave A" <da**@sigmasolutionsdonotspamme.com.au> wrote in message
news:Oo****************@TK2MSFTNGP10.phx.gbl...I have a class called 'PrimaryKey' that represents the primary key of a
table.
PrimaryKeys can only be created and the class only implements
.ToString().
The PrimaryKey class internally stores the data as either a int or a
Guid
depending on the structure of the database.
If we simply used int to represent a primary key, rather than this
PrimaryKey class then programmers could do things like performing
mathematically operations on the primary key which should be best
avoided
since this is not the nature of primary keys.
The PrimaryKey class works really well except when it comes to exposing
it
through SOAP. Because the class contains no public fields and no public
properties then SOAP/WSDL does not expose any insights into the class.
When an instance of the PrimaryKey class flows through SOAP and turns up
at the client I can't actually do anything with it since I can't get any
data out of it and cast it into the client's PrimaryKey class.
Ideally I would to put an attribute around the 'private int primaryKey'
field of the PrimaryKey class (that internally records the value of the
primary key) so that it can be exposed to SOAP and SOAP alone.
Is this possible? I have studied the SOAP attributes and nothing seems
available. Are there any work arounds?
One idea I had was to drop the .ToString() method and just have a .Value
property. I would only implement the Get and not the Set but evidently
SOAP/WSDL needs both a Get and a Set before it is exposed to SOAP.
Thanks in advance
Dave A
I knew there had to be an answer and there is!
It just barely works with .NET 1.x - http://dotnetified.com/PermaLink.asp...F-CDA36ACF481F
And it fully works with .NET
2.0 -http://weblogs.asp.net/cweyer/archive/2004/08/02/205798.aspx
Dave A
('Exposing private members using SOAP and XML Serialization' - that is there
for google)
"Dave A" <da**@sigmasolutionsdonotspamme.com.au> wrote in message
news:%2****************@TK2MSFTNGP10.phx.gbl... Thanks. I appreciate the effort that you put into that great answer.
There has to be a solution though. I am going to keep thinking about it
and if I come up with something then I will post back what I find.
"Sami Vaaraniemi" <sa**********@pleasejippii.fi> wrote in message
news:eL**************@TK2MSFTNGP09.phx.gbl... I'm afraid there's no simple and easy answer to this issue. As you've
noticed, the XML serializer serializes only public fields and read-write
properties. The data format is customizable to some extent, but all
private state and behavior associated with your classes is lost.
That said, it is possible to hack around this issue. You can edit the
consumer-side proxy, remove the data classes generated along with the
proxy and have the proxy refer to the original class(es). This does allow
you to share the same type between the web service and the consumer and
thus share behavior, but private state is still lost.
The bottom line is that if you really want to share objects between a
service and its consumers, then you might want to consider using a
distributed object technology such as .NET Remoting. Web Services merely
pass XML documents back and forth, and trying to share types or behavior
will run into issues.
Regards,
Sami
"Dave A" <da**@sigmasolutionsdonotspamme.com.au> wrote in message
news:Oo****************@TK2MSFTNGP10.phx.gbl...I have a class called 'PrimaryKey' that represents the primary key of a
table.
PrimaryKeys can only be created and the class only implements
.ToString().
The PrimaryKey class internally stores the data as either a int or a
Guid
depending on the structure of the database.
If we simply used int to represent a primary key, rather than this
PrimaryKey class then programmers could do things like performing
mathematically operations on the primary key which should be best
avoided
since this is not the nature of primary keys.
The PrimaryKey class works really well except when it comes to exposing
it
through SOAP. Because the class contains no public fields and no public
properties then SOAP/WSDL does not expose any insights into the class.
When an instance of the PrimaryKey class flows through SOAP and turns up
at the client I can't actually do anything with it since I can't get any
data out of it and cast it into the client's PrimaryKey class.
Ideally I would to put an attribute around the 'private int primaryKey'
field of the PrimaryKey class (that internally records the value of the
primary key) so that it can be exposed to SOAP and SOAP alone.
Is this possible? I have studied the SOAP attributes and nothing seems
available. Are there any work arounds?
One idea I had was to drop the .ToString() method and just have a .Value
property. I would only implement the Get and not the Set but evidently
SOAP/WSDL needs both a Get and a Set before it is exposed to SOAP.
Thanks in advance
Dave A
Indeed, you can serialize a private field as shown in the article by
overriding the serialization for the object. You could also do this with a
wrapper class and a bit of reflection.
However, (I think) in the consumer the field now becomes public in the
generated class so the behavior (encapsulation) is lost. The consumer will
be able to access the PrimaryKey value directly which is what I believe you
wanted to avoid.
Regards,
Sami
"Dave A" <da**@sigmasolutionsdonotspamme.com.au> wrote in message
news:OI**************@TK2MSFTNGP15.phx.gbl... I knew there had to be an answer and there is!
It just barely works with .NET 1.x -
http://dotnetified.com/PermaLink.asp...F-CDA36ACF481F
And it fully works with .NET
2.0 -http://weblogs.asp.net/cweyer/archive/2004/08/02/205798.aspx
Dave A
('Exposing private members using SOAP and XML Serialization' - that is
there for google)
"Dave A" <da**@sigmasolutionsdonotspamme.com.au> wrote in message
news:%2****************@TK2MSFTNGP10.phx.gbl... Thanks. I appreciate the effort that you put into that great answer.
There has to be a solution though. I am going to keep thinking about it
and if I come up with something then I will post back what I find.
"Sami Vaaraniemi" <sa**********@pleasejippii.fi> wrote in message
news:eL**************@TK2MSFTNGP09.phx.gbl... I'm afraid there's no simple and easy answer to this issue. As you've
noticed, the XML serializer serializes only public fields and read-write
properties. The data format is customizable to some extent, but all
private state and behavior associated with your classes is lost.
That said, it is possible to hack around this issue. You can edit the
consumer-side proxy, remove the data classes generated along with the
proxy and have the proxy refer to the original class(es). This does
allow you to share the same type between the web service and the
consumer and thus share behavior, but private state is still lost.
The bottom line is that if you really want to share objects between a
service and its consumers, then you might want to consider using a
distributed object technology such as .NET Remoting. Web Services merely
pass XML documents back and forth, and trying to share types or behavior
will run into issues.
Regards,
Sami
"Dave A" <da**@sigmasolutionsdonotspamme.com.au> wrote in message
news:Oo****************@TK2MSFTNGP10.phx.gbl...
I have a class called 'PrimaryKey' that represents the primary key of a
table.
PrimaryKeys can only be created and the class only implements
.ToString().
The PrimaryKey class internally stores the data as either a int or a
Guid
depending on the structure of the database.
If we simply used int to represent a primary key, rather than this
PrimaryKey class then programmers could do things like performing
mathematically operations on the primary key which should be best
avoided
since this is not the nature of primary keys.
The PrimaryKey class works really well except when it comes to exposing
it
through SOAP. Because the class contains no public fields and no
public
properties then SOAP/WSDL does not expose any insights into the class.
When an instance of the PrimaryKey class flows through SOAP and turns
up
at the client I can't actually do anything with it since I can't get
any
data out of it and cast it into the client's PrimaryKey class.
Ideally I would to put an attribute around the 'private int primaryKey'
field of the PrimaryKey class (that internally records the value of the
primary key) so that it can be exposed to SOAP and SOAP alone.
Is this possible? I have studied the SOAP attributes and nothing seems
available. Are there any work arounds?
One idea I had was to drop the .ToString() method and just have a
.Value
property. I would only implement the Get and not the Set but evidently
SOAP/WSDL needs both a Get and a Set before it is exposed to SOAP.
Thanks in advance
Dave A
Indeed, you can serialize a private field as shown in the article by
overriding the serialization for the object. You could also do this with a
wrapper class and a bit of reflection.
However, (I think) in the consumer the field now becomes public in the
generated class so the behavior (encapsulation) is lost. The consumer will
be able to access the PrimaryKey value directly which is what I believe you
wanted to avoid.
Regards,
Sami
"Dave A" <da**@sigmasolutionsdonotspamme.com.au> wrote in message
news:OI**************@TK2MSFTNGP15.phx.gbl... I knew there had to be an answer and there is!
It just barely works with .NET 1.x -
http://dotnetified.com/PermaLink.asp...F-CDA36ACF481F
And it fully works with .NET
2.0 -http://weblogs.asp.net/cweyer/archive/2004/08/02/205798.aspx
Dave A
('Exposing private members using SOAP and XML Serialization' - that is
there for google)
"Dave A" <da**@sigmasolutionsdonotspamme.com.au> wrote in message
news:%2****************@TK2MSFTNGP10.phx.gbl... Thanks. I appreciate the effort that you put into that great answer.
There has to be a solution though. I am going to keep thinking about it
and if I come up with something then I will post back what I find.
"Sami Vaaraniemi" <sa**********@pleasejippii.fi> wrote in message
news:eL**************@TK2MSFTNGP09.phx.gbl... I'm afraid there's no simple and easy answer to this issue. As you've
noticed, the XML serializer serializes only public fields and read-write
properties. The data format is customizable to some extent, but all
private state and behavior associated with your classes is lost.
That said, it is possible to hack around this issue. You can edit the
consumer-side proxy, remove the data classes generated along with the
proxy and have the proxy refer to the original class(es). This does
allow you to share the same type between the web service and the
consumer and thus share behavior, but private state is still lost.
The bottom line is that if you really want to share objects between a
service and its consumers, then you might want to consider using a
distributed object technology such as .NET Remoting. Web Services merely
pass XML documents back and forth, and trying to share types or behavior
will run into issues.
Regards,
Sami
"Dave A" <da**@sigmasolutionsdonotspamme.com.au> wrote in message
news:Oo****************@TK2MSFTNGP10.phx.gbl...
I have a class called 'PrimaryKey' that represents the primary key of a
table.
PrimaryKeys can only be created and the class only implements
.ToString().
The PrimaryKey class internally stores the data as either a int or a
Guid
depending on the structure of the database.
If we simply used int to represent a primary key, rather than this
PrimaryKey class then programmers could do things like performing
mathematically operations on the primary key which should be best
avoided
since this is not the nature of primary keys.
The PrimaryKey class works really well except when it comes to exposing
it
through SOAP. Because the class contains no public fields and no
public
properties then SOAP/WSDL does not expose any insights into the class.
When an instance of the PrimaryKey class flows through SOAP and turns
up
at the client I can't actually do anything with it since I can't get
any
data out of it and cast it into the client's PrimaryKey class.
Ideally I would to put an attribute around the 'private int primaryKey'
field of the PrimaryKey class (that internally records the value of the
primary key) so that it can be exposed to SOAP and SOAP alone.
Is this possible? I have studied the SOAP attributes and nothing seems
available. Are there any work arounds?
One idea I had was to drop the .ToString() method and just have a
.Value
property. I would only implement the Get and not the Set but evidently
SOAP/WSDL needs both a Get and a Set before it is exposed to SOAP.
Thanks in advance
Dave A
This thread has been closed and replies have been disabled. Please start a new discussion. Similar topics
by: Chris |
last post by:
Hi,
I'm trying to append text from another class to a generic richTextBox that
I've added to a Windows form. I can't seem to figure out how to expose the
richTextBox to append text to it.
...
|
by: J L |
last post by:
I'm trying to expose only a limited set of method calls from a C#
program to someone using my dll.
The entire application is written in C# and my first attempt has been to
try and write a COM...
|
by: John |
last post by:
Hi
How can I expose procedures (function or sub) in my vb.net app to vba in
word?
Thanks
Regards
|
by: Dhananjayan |
last post by:
Hi,
I have a webservice(eg.IStringServicePort) running on Axis, iam able to
create a java client for the same and invoke the service and obtain the
result.
I wanted to create a .Net client(C#)...
|
by: Dave A |
last post by:
I have a class called 'PrimaryKey' that represents the primary key of a
table.
PrimaryKeys can only be created and the class only implements .ToString().
The PrimaryKey class internally stores...
|
by: Dica |
last post by:
Hi all
I've got a java microEdition client trying to make soap requests to my .Net
service. i keep getting "Server was unable to process request..." err msg
when attempting to make the request....
|
by: archana |
last post by:
Hi all,
can anyone tell me differene between public static and private static
method.
how they are allocated and access?.
thanks in advance.
|
by: =?Utf-8?B?QkogU2FmZGll?= |
last post by:
We have a class that has a public property that is of type List<T>. FXCop
generates a DoNotExposeGenericLists error, indicating
"System.Collections.Generic.List<Tis a generic collection designed...
|
by: =?Utf-8?B?RGFuTQ==?= |
last post by:
Can someone help with the following problem. I am sending an encrypted SOAP
message to a .NET 2.0 + WSE 3.0 web service. When .NET attempts to decrypt
the message it cannot read the private key...
|
by: Charles Arthur |
last post by:
How do i turn on java script on a villaon, callus and itel keypad mobile phone
|
by: nemocccc |
last post by:
hello, everyone, I want to develop a software for my android phone for daily needs, any suggestions?
|
by: Sonnysonu |
last post by:
This is the data of csv file
1 2 3
1 2 3
1 2 3
1 2 3
2 3
2 3
3
the lengths should be different i have to store the data by column-wise with in the specific length.
suppose the i have to...
|
by: Hystou |
last post by:
There are some requirements for setting up RAID:
1. The motherboard and BIOS support RAID configuration.
2. The motherboard has 2 or more available SATA protocol SSD/HDD slots (including MSATA, M.2...
|
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,...
|
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,...
|
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...
|
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...
|
by: agi2029 |
last post by:
Let's talk about the concept of autonomous AI software engineers and no-code agents. These AIs are designed to manage the entire lifecycle of a software development project—planning, coding, testing,...
| |
