I've tried in a few places using a variable name Form and it appears to be
OK.
For example:
Public Shared Sub WritePositionsInRegistry(ByVal Form As Form, ByVal
SubkeyName As String)
Is it OK to use a Type name as a variable name. For example,:
Set(ByVal Color As Color)
Sometimes I can't think of a fitting argument name other then the Type name.
Thanks 21 1719
It would be considered very bad form to write a program this way. Since a
lot of Type names have shared function that can called directly, it makes
your program hard to read. Espcially when you can fix the problem with a
simple prefix.
Public Shared Sub WritePositionsInRegistry(ByVal frmForm As Form, ByVal
SubkeyName As String)
Just my two cents
Chris
" Just Me" <gr****@a-znet.com> wrote in message
news:OC**************@tk2msftngp13.phx.gbl... I've tried in a few places using a variable name Form and it appears to be OK. For example: Public Shared Sub WritePositionsInRegistry(ByVal Form As Form, ByVal SubkeyName As String)
Is it OK to use a Type name as a variable name. For example,:
Set(ByVal Color As Color)
Sometimes I can't think of a fitting argument name other then the Type name. Thanks
Just Me,
There are a group of developers, such as Chris, who feel that using the type
name for the variable is a bad thing. There are another group of developers,
usually OO developers, who feel using the type name for the variable name
may be a good idea.
I tend to fall into this second group, as that is the way I interpret the
"Parameter Naming Guidelines" http://msdn.microsoft.com/library/de...Guidelines.asp
from the ".NET Design Guidelines for Class Library Developers".
Naming the parameter for the type may be the best fit because its:
- a descriptive name - 'form' may be the most descriptive name for variable
given how its used. parentForm or childForm may be better names.
- describe a parameter's meaning - IMHO its obvious 'form' means form. :-)
- Do not prefix parameter names with Hungarian type notation (IMHO frmForm
is "duplication", a number of OO developers try to avoid duplication, its
avoid duplication is a major tenent of Refactoring http://www.refactoring.com)
Also the above guidelines suggest not to abbreviate names, 'form' is better
then 'frm'. Is frm short for Form, Farm, or Functional Resources Manager? http://msdn.microsoft.com/library/de...reviations.asp
In other words, rather then frmForm as Chris suggests I would consider
formParent, or parentForm. Depending on what I am doing would decide if I
use the type as a prefix or suffix... Sometimes I simply use parent or child
if its "obvious" in the context what the variable represents, remember the
type of the variable also contributes to the meaning of the variable...
There is another group of developers, mostly Java, that prefer to prefix the
name with "the", "a" or "an" ("a" as in singular not a Hungarian array
prefix), which makes the code "easier" to read as English.
Public Shared Sub WritePositionsInRegistry(ByVal theForm As Form)
For Each aChild As Control in theForm.Controls
aChild.BackColor = theForm.BackColor
Next
End Sub
You find "the", "a", and "an" a lot in Martin Fowler's Refactoring book, as
all the samples are in Java.
If my shop had a perceived need for prefixes (Hungarian hold overs) I would
promote the third method, for its perceived readability...
Hope this helps
Jay
" Just Me" <gr****@a-znet.com> wrote in message
news:OC**************@tk2msftngp13.phx.gbl... I've tried in a few places using a variable name Form and it appears to be OK. For example: Public Shared Sub WritePositionsInRegistry(ByVal Form As Form, ByVal SubkeyName As String)
Is it OK to use a Type name as a variable name. For example,:
Set(ByVal Color As Color)
Sometimes I can't think of a fitting argument name other then the Type name. Thanks
I agree that frmForm is redunant. frmMain is how I have always done it, but
this is from someone that has not had to work in a company with large teams
and had to standardize naming conventions. Very nice write-up on this idea
Jay.
Chris
"Jay B. Harlow [MVP - Outlook]" <Ja************@msn.com> wrote in message
news:%2****************@TK2MSFTNGP09.phx.gbl... Just Me, There are a group of developers, such as Chris, who feel that using the type name for the variable is a bad thing. There are another group of developers, usually OO developers, who feel using the type name for the variable name may be a good idea.
I tend to fall into this second group, as that is the way I interpret the "Parameter Naming Guidelines" http://msdn.microsoft.com/library/de...Guidelines.asp from the ".NET Design Guidelines for Class Library Developers".
Naming the parameter for the type may be the best fit because its: - a descriptive name - 'form' may be the most descriptive name for variable given how its used. parentForm or childForm may be better names. - describe a parameter's meaning - IMHO its obvious 'form' means form. :-) - Do not prefix parameter names with Hungarian type notation (IMHO frmForm is "duplication", a number of OO developers try to avoid duplication, its avoid duplication is a major tenent of Refactoring http://www.refactoring.com)
Also the above guidelines suggest not to abbreviate names, 'form' is better then 'frm'. Is frm short for Form, Farm, or Functional Resources Manager?
http://msdn.microsoft.com/library/de...reviations.asp
In other words, rather then frmForm as Chris suggests I would consider formParent, or parentForm. Depending on what I am doing would decide if I use the type as a prefix or suffix... Sometimes I simply use parent or child if its "obvious" in the context what the variable represents, remember the type of the variable also contributes to the meaning of the variable...
There is another group of developers, mostly Java, that prefer to prefix the name with "the", "a" or "an" ("a" as in singular not a Hungarian array prefix), which makes the code "easier" to read as English.
Public Shared Sub WritePositionsInRegistry(ByVal theForm As Form) For Each aChild As Control in theForm.Controls aChild.BackColor = theForm.BackColor Next End Sub
You find "the", "a", and "an" a lot in Martin Fowler's Refactoring book, as all the samples are in Java.
If my shop had a perceived need for prefixes (Hungarian hold overs) I would promote the third method, for its perceived readability...
Hope this helps Jay
" Just Me" <gr****@a-znet.com> wrote in message news:OC**************@tk2msftngp13.phx.gbl... I've tried in a few places using a variable name Form and it appears to be OK. For example: Public Shared Sub WritePositionsInRegistry(ByVal Form As Form, ByVal SubkeyName As String)
Is it OK to use a Type name as a variable name. For example,:
Set(ByVal Color As Color)
Sometimes I can't think of a fitting argument name other then the Type name. Thanks
" Just Me" <gr****@a-znet.com> wrote Is it OK to use a Type name as a variable name. For example,:
Since it works, that must mean MS has decided it is OK. You
also have the option of rebooting the user's computer when your
application ends. That also is allowed.
But there is a difference between what is allowed, and what makes
for common/practical sense. In one case, its a hassle for the user,
and in the other, a hassle for the next guy who looks at your code.
Set(ByVal Color As Color)
Sometimes I can't think of a fitting argument name other then the Type name.
Set ??? Set what? Typically, generic names fit well in those situations:
ForeColor(ByVal Value As Color)
LFS
Larry,
"Larry Serflaten" <se*******@usinternet.com> schrieb: Since it works, that must mean MS has decided it is OK. You also have the option of rebooting the user's computer when your application ends. That also is allowed.
But there is a difference between what is allowed, and what makes for common/practical sense. In one case, its a hassle for the user, and in the other, a hassle for the next guy who looks at your code.
JFMI: How would you name the first parameter of the method
'SetComboBoxPasswordChar' in this snippet?
Enabling a password char for a combobox control
<URL:http://dotnet.mvps.org/dotnet/faqs/?id=comboboxpasswordchar&lang=en>
--
M S Herfried K. Wagner
M V P <URL:http://dotnet.mvps.org/>
V B <URL:http://dotnet.mvps.org/dotnet/faqs/>
Herfried,
What is JFMI?
I would name it "comboBox" (lower case c instead of Upper case C) as I don't
see any other name that is more descriptive or meaning full given the
context...
Jay
"Herfried K. Wagner [MVP]" <hi***************@gmx.at> wrote in message
news:OU**************@TK2MSFTNGP11.phx.gbl... Larry,
"Larry Serflaten" <se*******@usinternet.com> schrieb: Since it works, that must mean MS has decided it is OK. You also have the option of rebooting the user's computer when your application ends. That also is allowed.
But there is a difference between what is allowed, and what makes for common/practical sense. In one case, its a hassle for the user, and in the other, a hassle for the next guy who looks at your code.
JFMI: How would you name the first parameter of the method 'SetComboBoxPasswordChar' in this snippet?
Enabling a password char for a combobox control <URL:http://dotnet.mvps.org/dotnet/faqs/?id=comboboxpasswordchar&lang=en>
-- M S Herfried K. Wagner M V P <URL:http://dotnet.mvps.org/> V B <URL:http://dotnet.mvps.org/dotnet/faqs/>
"Herfried K. Wagner [MVP]" <hi***************@gmx.at> wrote JFMI: How would you name the first parameter of the method 'SetComboBoxPasswordChar' in this snippet?
Enabling a password char for a combobox control <URL:http://dotnet.mvps.org/dotnet/faqs/?id=comboboxpasswordchar&lang=en>
Since this routine operates on any combobox, the parameter has to target which
combo box is desired, hense: Target
But for that second parameter, its the character that is needed, is it not?
Shouldn't that parameter's name simply be Character?
LFS
"Jay B. Harlow [MVP - Outlook]" <Ja************@msn.com> wrote There are a group of developers, such as Chris, who feel that using the type name for the variable is a bad thing. There are another group of developers, usually OO developers, who feel using the type name for the variable name may be a good idea.
I tend to fall into this second group, as that is the way I interpret the "Parameter Naming Guidelines"
Naming the parameter for the type may be the best fit because its: - a descriptive name - 'form' may be the most descriptive name for variable given how its used. parentForm or childForm may be better names. - describe a parameter's meaning - IMHO its obvious 'form' means form. :-) - Do not prefix parameter names with Hungarian type notation (IMHO frmForm is "duplication", a number of OO developers try to avoid duplication, its avoid duplication is a major tenent of Refactoring http://www.refactoring.com)
Did you miss this from the naming guidelines:
-Use names that describe a parameter's meaning rather than names that describe a parameter's type.
Public Shared Sub WritePositionsInRegistry(ByVal theForm As Form) For Each aChild As Control in theForm.Controls aChild.BackColor = theForm.BackColor Next End Sub
Here, the form is the source object for the controls that will be saved, so, IMHO,
the parameter name could be "Source"
Public Shared Sub WritePositionsInRegistry(ByVal Source As Form)
Also, I do not favor camel case for parameter names. I do favor camel case
for local variables, and the parameter might be considered a local variable, but
for all practical purposes, it is sent from the outside world, and shows up in
intellisence formated as supplied. I prefer seeing proper case in parameters,
case in point:
Dim x As String = Chr(65)
The parameter for Chr is "CharCode" not "charCode", similarly for Asc.
(However other parts do show camel cased parameters....)
LFS
Jay,
"Jay B. Harlow [MVP - Outlook]" <Ja************@msn.com> schrieb: What is JFMI?
"Just for my information" ;-))).
I would name it "comboBox" (lower case c instead of Upper case C) as I don't see any other name that is more descriptive or meaning full given the context...
That's what I thought too, but I didn't use the lower case "c" because I
don't like the camel case naming convention ;-))).
--
M S Herfried K. Wagner
M V P <URL:http://dotnet.mvps.org/>
V B <URL:http://dotnet.mvps.org/dotnet/faqs/>
Larry,
"Larry Serflaten" <se*******@usinternet.com> schrieb: Enabling a password char for a combobox control <URL:http://dotnet.mvps.org/dotnet/faqs/?id=comboboxpasswordchar&lang=en>
Since this routine operates on any combobox, the parameter has to target which combo box is desired, hense: Target
But for that second parameter, its the character that is needed, is it not? Shouldn't that parameter's name simply be Character?
Both are interesting points I should consider :-)!
--
M S Herfried K. Wagner
M V P <URL:http://dotnet.mvps.org/>
V B <URL:http://dotnet.mvps.org/dotnet/faqs/>
Larry, Did you miss this from the naming guidelines:
-Use names that describe a parameter's meaning rather than names that describe a parameter's type.
Yep sure did, Oh! wait, it was the second point I made! - describe a parameter's meaning - IMHO its obvious 'form' means form. :-)
Also, I do not favor camel case for parameter names. I do favor camel case
I hope you will understand that "splitting hairs" is not my game, have a
nice day.
camelCase or ProperCase parameters is immaterial to the question! Hence
there is no reason to discuss it.
Hope this helps
Jay
"Larry Serflaten" <se*******@usinternet.com> wrote in message
news:OI**************@TK2MSFTNGP11.phx.gbl... "Jay B. Harlow [MVP - Outlook]" <Ja************@msn.com> wrote
There are a group of developers, such as Chris, who feel that using the type name for the variable is a bad thing. There are another group of developers, usually OO developers, who feel using the type name for the variable name may be a good idea.
I tend to fall into this second group, as that is the way I interpret the "Parameter Naming Guidelines"
Naming the parameter for the type may be the best fit because its: - a descriptive name - 'form' may be the most descriptive name for variable given how its used. parentForm or childForm may be better names. - describe a parameter's meaning - IMHO its obvious 'form' means form. :-) - Do not prefix parameter names with Hungarian type notation (IMHO frmForm is "duplication", a number of OO developers try to avoid duplication, its avoid duplication is a major tenent of Refactoring http://www.refactoring.com)
Did you miss this from the naming guidelines:
-Use names that describe a parameter's meaning rather than names that describe a parameter's type.
Public Shared Sub WritePositionsInRegistry(ByVal theForm As Form) For Each aChild As Control in theForm.Controls aChild.BackColor = theForm.BackColor Next End Sub
Here, the form is the source object for the controls that will be saved, so, IMHO, the parameter name could be "Source"
Public Shared Sub WritePositionsInRegistry(ByVal Source As Form)
Also, I do not favor camel case for parameter names. I do favor camel case for local variables, and the parameter might be considered a local variable, but for all practical purposes, it is sent from the outside world, and shows up in intellisence formated as supplied. I prefer seeing proper case in parameters, case in point:
Dim x As String = Chr(65)
The parameter for Chr is "CharCode" not "charCode", similarly for Asc. (However other parts do show camel cased parameters....)
LFS
"Jay B. Harlow [MVP - Outlook]" <Ja************@msn.com> wrote I tend to fall into this second group, as that is the way I interpret the "Parameter Naming Guidelines"
<...> - describe a parameter's meaning - IMHO its obvious 'form' means form.
(From: -Use names that describe a parameter's meaning rather than names that
describe a parameter's type.)
Interesting interpretation. What does form mean, exactly? If you say it means
that a form is supposed to be passed in, you are describing the parameter's type.
So I have to ask, what does 'form As Form' tell you about the parameter, other
than it is supposed to be of the type Form?
LFS
Just Me,
For me it is very simple, anything that can give misunderstandings too
another than myself is bad to use.
Wheter it does give a program error or not is not important in that.
When there is extra time needed to understand a program, while that could
have been avoided with good names, than in my opinion the programmer who did
that is a bad programmer.
Using "dim form as form" comes in my opinion in that category, some playing
of the programmer to statify himself (the Dutch word express it better
because that has two meanings).
Just my thought,
Cor
" Just Me" <gr****@a-znet.com> I've tried in a few places using a variable name Form and it appears to be OK. For example: Public Shared Sub WritePositionsInRegistry(ByVal Form As Form, ByVal SubkeyName As String)
Is it OK to use a Type name as a variable name. For example,:
Set(ByVal Color As Color)
Sometimes I can't think of a fitting argument name other then the Type name. Thanks
"Larry Serflaten" <se*******@usinternet.com> wrote in message
news:u8**************@tk2msftngp13.phx.gbl... " Just Me" <gr****@a-znet.com> wrote Is it OK to use a Type name as a variable name. For example,:
Since it works, that must mean MS has decided it is OK. You also have the option of rebooting the user's computer when your application ends. That also is allowed.
But there is a difference between what is allowed, and what makes for common/practical sense. In one case, its a hassle for the user, and in the other, a hassle for the next guy who looks at your code.
Set(ByVal color As Color)
A property Sometimes I can't think of a fitting argument name other then the Type name.
Set ??? Set what? Typically, generic names fit well in those situations:
ForeColor(ByVal Value As Color)
LFS
Thanks for the answers that were directed to help me.
I too don't like the camel naming convention but I believe all MS methods
use it so I may just to be consistent (so IntelliSense of mine and MS's look
the same).
Also
Bevel color as Color
and
something = color
Seems to me a clear as
Bevel the as Color
and
something = the
Also I've been using Main and Cancel instead of formalin and btnCancel and
grew to like it better this way.
But I can tell from the replies everyone does not agree which are the best
methods.
My problem was more basic then the answers implied - I was just wondering if
it was OK in the sense: does it work OK!
Thanks
" Just Me" <gr****@a-znet.com> wrote in message
news:OC**************@tk2msftngp13.phx.gbl... I've tried in a few places using a variable name Form and it appears to be OK. For example: Public Shared Sub WritePositionsInRegistry(ByVal Form As Form, ByVal SubkeyName As String)
Is it OK to use a Type name as a variable name. For example,:
Set(ByVal color As Color)
Sometimes I can't think of a fitting argument name other then the Type name. Thanks
Just Me, My problem was more basic then the answers implied - I was just wondering if it was OK in the sense: does it work OK!
Yes the compiler allows you to name variables, parameters, fields, &
properties for types.
I have yet to see an actual negative side effect to using the same name. The
closest negative side effect is the Shared member "problem" that was
mentioned, however the compiler is smart enough to create valid IL, so there
is no actual "problem"...
An annoyance of using the type as the variable name, is the Intellisense
gets confused, however this does not impact the IL created...
Also I've been using Main and Cancel instead of formalin and btnCancel and grew to like it better this way.
I normally suffix my forms with Form or Dialog depending on if its a "Form"
or a "Dialog". For example MainForm & OptionsDialog.
I use Form.Show to show forms, while I use Form.Dialog to use dialogs.
For buttons I have been spelling out the type as in "buttonCancel", however
I see a certain appeal in simply calling it "Cancel". I have a Timer in a
Service that I have simply named "ScanWait", the code actually reads rather
nicely.
ScanWait.Start
Sub ScanWait_Elapsed
Dim wait As TimeSpan = ...
ScanWait.Interval = wait.TotalMilliseconds
Hope this helps
Jay
" Just Me" <gr****@a-znet.com> wrote in message
news:%2****************@TK2MSFTNGP15.phx.gbl... Thanks for the answers that were directed to help me.
I too don't like the camel naming convention but I believe all MS methods use it so I may just to be consistent (so IntelliSense of mine and MS's look the same).
Also Bevel color as Color and something = color
Seems to me a clear as Bevel the as Color and something = the
Also I've been using Main and Cancel instead of formalin and btnCancel and grew to like it better this way.
But I can tell from the replies everyone does not agree which are the best methods.
My problem was more basic then the answers implied - I was just wondering if it was OK in the sense: does it work OK!
Thanks
<<snip>>
Jay,
"Jay B. Harlow [MVP - Outlook]" <Ja************@msn.com> schrieb: I use Form.Show to show forms, while I use Form.Dialog to use dialogs.
I assume you use 'Form.ShowDialog' for showing dialogs :-).
--
Herfried K. Wagner [MVP]
<URL:http://dotnet.mvps.org/>
Herfried,
Doh!!
Yes I use Form.ShowDialog for showing dialogs...
Thanks for the assist...
Jay
"Herfried K. Wagner [MVP]" <hi***************@gmx.at> wrote in message
news:%2****************@TK2MSFTNGP11.phx.gbl... Jay,
"Jay B. Harlow [MVP - Outlook]" <Ja************@msn.com> schrieb: I use Form.Show to show forms, while I use Form.Dialog to use dialogs.
I assume you use 'Form.ShowDialog' for showing dialogs :-).
-- Herfried K. Wagner [MVP] <URL:http://dotnet.mvps.org/> An annoyance of using the type as the variable name, is the Intellisense gets confused
I haven't seen signs of confusion.
I'm now looking at an Intellisense:
WritePositionsInRegistry(form As SystemsWindowsForms.Form, subKeyName as
String)
Looks good to me!
What do you think?
PS
I said
"I too don't like the camel naming convention "
but I mean aesthetically
I do like the fact that variables look different then Classes, Properties
and Functions for which I use Pascal naming.
Just Me,
In VS.NET 2003 when you use "form As Form", sometimes (not always) VB.NET
will change it to "from As form" and refuse to change the case of the type.
Using fully qualified names as you did, does not have this problem.
So "intellisense" might have been the wrong term its more the "Pretty
listing (reformatting) of code" option that gets confused...
Hope this helps
Jay
" Just Me" <gr****@a-znet.com> wrote in message
news:%2***************@TK2MSFTNGP12.phx.gbl... An annoyance of using the type as the variable name, is the Intellisense gets confused
I haven't seen signs of confusion. I'm now looking at an Intellisense:
WritePositionsInRegistry(form As SystemsWindowsForms.Form, subKeyName as String)
Looks good to me!
What do you think?
PS I said "I too don't like the camel naming convention " but I mean aesthetically I do like the fact that variables look different then Classes, Properties and Functions for which I use Pascal naming.
I think I may have seen that one time.
Thanks
"Jay B. Harlow [MVP - Outlook]" <Ja************@msn.com> wrote in message
news:%2****************@TK2MSFTNGP11.phx.gbl... Just Me, In VS.NET 2003 when you use "form As Form", sometimes (not always) VB.NET will change it to "from As form" and refuse to change the case of the type.
Using fully qualified names as you did, does not have this problem.
So "intellisense" might have been the wrong term its more the "Pretty listing (reformatting) of code" option that gets confused...
Hope this helps Jay
" Just Me" <gr****@a-znet.com> wrote in message news:%2***************@TK2MSFTNGP12.phx.gbl... An annoyance of using the type as the variable name, is the Intellisense gets confused
I haven't seen signs of confusion. I'm now looking at an Intellisense:
WritePositionsInRegistry(form As SystemsWindowsForms.Form, subKeyName as String)
Looks good to me!
What do you think?
PS I said "I too don't like the camel naming convention " but I mean aesthetically I do like the fact that variables look different then Classes, Properties and Functions for which I use Pascal naming.
This thread has been closed and replies have been disabled. Please start a new discussion. Similar topics
by: Rudi Groenewald |
last post by:
Hi there...
How do I get to extract info like, current Database logged in user or
general stats like, ram usage... etc etc etc into a form if I use Microsoft
Access 2002 for my forms...
|
by: LC's No-Spam Newsreading account |
last post by:
I have the following arrangement working under Netscape 3 / Unix, IE6 /
Win and Konqueror / Linux, but NOT under Netscape 7 Unix or Mozilla
Linux (silently fails) nor under Netscape 4 Unix (fails...
|
by: Darryl Kerkeslager |
last post by:
I don't do much with subforms - in fact I've deliberately avoided them - but
....
I have a tab control that will contain several subforms, each bound to a
separate table, and each table/subform...
|
by: Bhargavan |
last post by:
Hey Group,
When I minimize and then maximize a form (in windows application), I see a
significant drop in memory usuage in the task manager. I tried to do the
same thing programatically during the...
|
by: Yosh |
last post by:
I am using the Task Manager to monitor my application's memory usage.
Problem... when I run my application and display a form, the memory
increases. When I close the form, the memory is not...
|
by: Alex |
last post by:
Hello all,
I have a main form(say "form1") .i want to display another form(say
"form2") on occuring of an event (say a button click) and want to hide
it after some time so that it will again...
|
by: chrispy102 |
last post by:
Hi all,
I have an MDI app developed using vis studio 2005.
The problem I have is that evey time I close a Child form and open another, the CPU PF Usage increments slighty. This happens every time...
|
by: magix |
last post by:
Hi,
Can I:
<script language="javascript">
var TimeSec = new String (Request.form("TimeInSec"));
or
|
by: kimiraikkonen |
last post by:
Hi,
On my system which is 2.4GHZ P4 CPU, 1GB memory + 64MB DDR graphic
card, if i create a simple picturebox docked on a form sized about
500x350 or less or more, doesn't matter, and also if i...
|
by: dhtml |
last post by:
(originally mis-posted on m.p.s.jscript...)
I've just closed all windows in Firefox and its using 244MB of memory.
I have no idea why. I had GMail open, a page from unicode, the CLJ FAQ.
...
|
by: Charles Arthur |
last post by:
How do i turn on java script on a villaon, callus and itel keypad mobile phone
|
by: ryjfgjl |
last post by:
In our work, we often receive Excel tables with data in the same format. If we want to analyze these data, it can be difficult to analyze them because the data is spread across multiple Excel files...
|
by: emmanuelkatto |
last post by:
Hi All, I am Emmanuel katto from Uganda. I want to ask what challenges you've faced while migrating a website to cloud.
Please let me know.
Thanks!
Emmanuel
|
by: BarryA |
last post by:
What are the essential steps and strategies outlined in the Data Structures and Algorithms (DSA) roadmap for aspiring data scientists? How can individuals effectively utilize this roadmap to progress...
|
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:
Most computers default to English, but sometimes we require a different language, especially when relocating. Forgot to request a specific language before your computer shipped? No problem! You can...
|
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: 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,...
| |