Hi,
I compiled an application for the first time with no errors but following
warnings:
1) variable declaration withoit an 'AS':
Dim def()
2) variable 'myvar' is used before it has been assigned a value:
Dim myvar
......
If wk = 1 Then
myvar = "yes"
ElseIf wk = 2 Then
myvar = "no"
End If
.......
3) unused variable: myvar2
Warning 3) is easy to solve: remove it.
Warning 1): is it important to specify (e.g. dim def() as string)? Can this
cause a run-time error?
Warning 2): is this a problem? Can i leave it like this (i'm sure 'myvar'
will get a value, so no risk of run-time error ...)
Thanks for advice
Bob
11  974 
"Bob" <sd@qscsqschrieb:
I compiled an application for the first time with no errors but following
warnings:
1) variable declaration withoit an 'AS':
Dim def()
2) variable 'myvar' is used before it has been assigned a value:
Dim myvar
.....
If wk = 1 Then
myvar = "yes"
ElseIf wk = 2 Then
myvar = "no"
End If
......
3) unused variable: myvar2
Warning 3) is easy to solve: remove it.
Yes.
Warning 1): is it important to specify (e.g. dim def() as string)? Can
this cause a run-time error?
It's better to specify the type of the array elements because it will enable
the compiler to perform type checking:
\\\
Dim Numbers(...) As Integer
Numbers(0) = Me.TextBox1.Text
///
.... will raise a compile-time error if 'Option Strict' is enabled.
Warning 2): is this a problem? Can i leave it like this (i'm sure 'myvar'
will get a value, so no risk of run-time error ...)
This warning is IMO rather useless in VB because VB initializes Variables to
specified values implicitly. I typically disable this warning.
--
M S Herfried K. Wagner
M V P <URL:http://dotnet.mvps.org/>
V B <URL:http://dotnet.mvps.org/dotnet/faqs/>
Bob,
An addition to Herfrieds answer,
It is good investigate these warnings and not to solve them by intializing
with some dumb value as some like to do.
Use values inside the level you need them and don't declare them as done in
the old cobol time in top of a program (this Cobol method is partially
adepted by BASIC people too).
Set option explicit to On and code your program like that.
Cor
"Bob" <sd@qscsqschreef in bericht
news:%2****************@TK2MSFTNGP06.phx.gbl...
Hi,
I compiled an application for the first time with no errors but following
warnings:
1) variable declaration withoit an 'AS':
Dim def()
2) variable 'myvar' is used before it has been assigned a value:
Dim myvar
.....
If wk = 1 Then
myvar = "yes"
ElseIf wk = 2 Then
myvar = "no"
End If
......
3) unused variable: myvar2
Warning 3) is easy to solve: remove it.
Warning 1): is it important to specify (e.g. dim def() as string)? Can
this cause a run-time error?
Warning 2): is this a problem? Can i leave it like this (i'm sure 'myvar'
will get a value, so no risk of run-time error ...)
Thanks for advice
Bob
Thanks both
"Cor Ligthert [MVP]" <no************@planet.nlschreef in bericht
news:%2****************@TK2MSFTNGP05.phx.gbl...
Bob,
An addition to Herfrieds answer,
It is good investigate these warnings and not to solve them by intializing
with some dumb value as some like to do.
Use values inside the level you need them and don't declare them as done
in the old cobol time in top of a program (this Cobol method is partially
adepted by BASIC people too).
Set option explicit to On and code your program like that.
Cor
"Bob" <sd@qscsqschreef in bericht
news:%2****************@TK2MSFTNGP06.phx.gbl...
>Hi,
I compiled an application for the first time with no errors but following
warnings:
1) variable declaration withoit an 'AS':
Dim def()
2) variable 'myvar' is used before it has been assigned a value:
Dim myvar
.....
If wk = 1 Then
myvar = "yes"
ElseIf wk = 2 Then
myvar = "no"
End If
......
3) unused variable: myvar2
Warning 3) is easy to solve: remove it.
Warning 1): is it important to specify (e.g. dim def() as string)? Can
this cause a run-time error?
Warning 2): is this a problem? Can i leave it like this (i'm sure 'myvar'
will get a value, so no risk of run-time error ...)
Thanks for advice
Bob
"Herfried K. Wagner [MVP]" <hi***************@gmx.atwrote in message
news:u3**************@TK2MSFTNGP04.phx.gbl...
"Bob" <sd@qscsqschrieb:
>I compiled an application for the first time with no errors but following
warnings:
1) variable declaration withoit an 'AS':
Dim def()
2) variable 'myvar' is used before it has been assigned a value:
Dim myvar
.....
If wk = 1 Then
myvar = "yes"
ElseIf wk = 2 Then
myvar = "no"
End If
......
3) unused variable: myvar2
Warning 3) is easy to solve: remove it.
Yes.
>Warning 1): is it important to specify (e.g. dim def() as string)? Can
this cause a run-time error?
It's better to specify the type of the array elements because it will
enable the compiler to perform type checking:
\\\
Dim Numbers(...) As Integer
Numbers(0) = Me.TextBox1.Text
///
... will raise a compile-time error if 'Option Strict' is enabled.
>Warning 2): is this a problem? Can i leave it like this (i'm sure 'myvar'
will get a value, so no risk of run-time error ...)
This warning is IMO rather useless in VB because VB initializes Variables
to specified values implicitly. I typically disable this warning.
I agree that it is mostly useless but in this case it makes sense since the
variable in question is a string and hence gets initalized to Nothing. The
if statement in Bob's post doesn't assign a value to it if wk is anything
else than 1 or 2 so there is a high potentional for a
NullReferenceException. Bob didn't post the code where the compiler
complains though so hard to tell if there might be a problem. Consider the
following:
Dim wk As Integer = 5
Dim myvar As String
If wk = 1 Then
myvar = "yes"
ElseIf wk = 2 Then
myvar = "no"
End If
myvar = myvar.Trim()
The compiler complains on the last row and if you ignore it you will get a
nice null reference exception when you run it.
/claes
Claes,
And in your solution probably an unwanted result?
I prefer the error.
Cor
"Claes Bergefall" <lo*****@nospam.nospamschreef in bericht
news:uZ**************@TK2MSFTNGP04.phx.gbl...
>
"Herfried K. Wagner [MVP]" <hi***************@gmx.atwrote in message
news:u3**************@TK2MSFTNGP04.phx.gbl...
>"Bob" <sd@qscsqschrieb:
>>I compiled an application for the first time with no errors but
following warnings:
1) variable declaration withoit an 'AS':
Dim def()
2) variable 'myvar' is used before it has been assigned a value:
Dim myvar
.....
If wk = 1 Then
myvar = "yes"
ElseIf wk = 2 Then
myvar = "no"
End If
......
3) unused variable: myvar2
Warning 3) is easy to solve: remove it.
Yes.
>>Warning 1): is it important to specify (e.g. dim def() as string)? Can
this cause a run-time error?
It's better to specify the type of the array elements because it will
enable the compiler to perform type checking:
\\\
Dim Numbers(...) As Integer
Numbers(0) = Me.TextBox1.Text
///
... will raise a compile-time error if 'Option Strict' is enabled.
>>Warning 2): is this a problem? Can i leave it like this (i'm sure
'myvar' will get a value, so no risk of run-time error ...)
This warning is IMO rather useless in VB because VB initializes Variables
to specified values implicitly. I typically disable this warning.
I agree that it is mostly useless but in this case it makes sense since
the variable in question is a string and hence gets initalized to Nothing.
The if statement in Bob's post doesn't assign a value to it if wk is
anything else than 1 or 2 so there is a high potentional for a
NullReferenceException. Bob didn't post the code where the compiler
complains though so hard to tell if there might be a problem. Consider the
following:
Dim wk As Integer = 5
Dim myvar As String
If wk = 1 Then
myvar = "yes"
ElseIf wk = 2 Then
myvar = "no"
End If
myvar = myvar.Trim()
The compiler complains on the last row and if you ignore it you will get a
nice null reference exception when you run it.
/claes
Hello Cor Ligthert [MVP],
I disagree with Cor on this point. Initializing a variable at instantiation
is something I really like.
Dim tValue As String
Dim tValue As String = String.Empty
Of the two statements above I prefer the latter. This guarantees that you
will actuially have a string (instead of Nothing).. it avoids the compiler
initialization warning.. and it makes it so you don't have to guess what
the variable holds since you initialize it right off the bat with a value
of your choosing. More than that.. the first statement has an unfinished
feel to it that makes my skin crawl.. like the programmer was lazy and did
a half-ass job.
-Boo
Bob,
An addition to Herfrieds answer,
It is good investigate these warnings and not to solve them by
intializing with some dumb value as some like to do.
Use values inside the level you need them and don't declare them as
done in the old cobol time in top of a program (this Cobol method is
partially adepted by BASIC people too).
Set option explicit to On and code your program like that.
Cor
"Bob" <sd@qscsqschreef in bericht
news:%2****************@TK2MSFTNGP06.phx.gbl...
>Hi,
I compiled an application for the first time with no errors but
following
warnings:
1) variable declaration withoit an 'AS':
Dim def()
2) variable 'myvar' is used before it has been assigned a value:
Dim myvar
.....
If wk = 1 Then
myvar = "yes"
ElseIf wk = 2 Then
myvar = "no"
End If
......
3) unused variable: myvar2
Warning 3) is easy to solve: remove it.
Warning 1): is it important to specify (e.g. dim def() as string)?
Can
this cause a run-time error?
Warning 2): is this a problem? Can i leave it like this (i'm sure
'myvar'
will get a value, so no risk of run-time error ...)
Thanks for advice
Bob
My sample code was to illustrate the danger in ignoring the warning. I don't
turn off the warning.
/claes
"Cor Ligthert [MVP]" <no************@planet.nlwrote in message
news:el**************@TK2MSFTNGP06.phx.gbl...
Claes,
And in your solution probably an unwanted result?
I prefer the error.
Cor
"Claes Bergefall" <lo*****@nospam.nospamschreef in bericht
news:uZ**************@TK2MSFTNGP04.phx.gbl...
>>
"Herfried K. Wagner [MVP]" <hi***************@gmx.atwrote in message
news:u3**************@TK2MSFTNGP04.phx.gbl...
>>"Bob" <sd@qscsqschrieb:
I compiled an application for the first time with no errors but
following warnings:
1) variable declaration withoit an 'AS':
Dim def()
2) variable 'myvar' is used before it has been assigned a value:
Dim myvar
.....
If wk = 1 Then
myvar = "yes"
ElseIf wk = 2 Then
myvar = "no"
End If
......
3) unused variable: myvar2
Warning 3) is easy to solve: remove it.
Yes.
Warning 1): is it important to specify (e.g. dim def() as string)? Can
this cause a run-time error?
It's better to specify the type of the array elements because it will
enable the compiler to perform type checking:
\\\
Dim Numbers(...) As Integer
Numbers(0) = Me.TextBox1.Text
///
... will raise a compile-time error if 'Option Strict' is enabled.
Warning 2): is this a problem? Can i leave it like this (i'm sure
'myvar' will get a value, so no risk of run-time error ...)
This warning is IMO rather useless in VB because VB initializes
Variables to specified values implicitly. I typically disable this
warning.
I agree that it is mostly useless but in this case it makes sense since
the variable in question is a string and hence gets initalized to
Nothing. The if statement in Bob's post doesn't assign a value to it if
wk is anything else than 1 or 2 so there is a high potentional for a
NullReferenceException. Bob didn't post the code where the compiler
complains though so hard to tell if there might be a problem. Consider
the following:
Dim wk As Integer = 5
Dim myvar As String
If wk = 1 Then
myvar = "yes"
ElseIf wk = 2 Then
myvar = "no"
End If
myvar = myvar.Trim()
The compiler complains on the last row and if you ignore it you will get
a nice null reference exception when you run it.
/claes
Sorry than Claes,
Than I probably did read it wrong,
Cor
"Claes Bergefall" <lo*****@nospam.nospamschreef in bericht
news:ug**************@TK2MSFTNGP06.phx.gbl...
My sample code was to illustrate the danger in ignoring the warning. I
don't turn off the warning.
/claes
"Cor Ligthert [MVP]" <no************@planet.nlwrote in message
news:el**************@TK2MSFTNGP06.phx.gbl...
>Claes,
And in your solution probably an unwanted result?
I prefer the error.
Cor
"Claes Bergefall" <lo*****@nospam.nospamschreef in bericht
news:uZ**************@TK2MSFTNGP04.phx.gbl...
>>>
"Herfried K. Wagner [MVP]" <hi***************@gmx.atwrote in message
news:u3**************@TK2MSFTNGP04.phx.gbl...
"Bob" <sd@qscsqschrieb:
I compiled an application for the first time with no errors but
following warnings:
1) variable declaration withoit an 'AS':
Dim def()
2) variable 'myvar' is used before it has been assigned a value:
Dim myvar
.....
If wk = 1 Then
myvar = "yes"
ElseIf wk = 2 Then
myvar = "no"
End If
......
3) unused variable: myvar2
>
>
Warning 3) is easy to solve: remove it.
Yes.
Warning 1): is it important to specify (e.g. dim def() as string)? Can
this cause a run-time error?
It's better to specify the type of the array elements because it will
enable the compiler to perform type checking:
\\\
Dim Numbers(...) As Integer
Numbers(0) = Me.TextBox1.Text
///
... will raise a compile-time error if 'Option Strict' is enabled.
Warning 2): is this a problem? Can i leave it like this (i'm sure
'myvar' will get a value, so no risk of run-time error ...)
This warning is IMO rather useless in VB because VB initializes
Variables to specified values implicitly. I typically disable this
warning.
I agree that it is mostly useless but in this case it makes sense since
the variable in question is a string and hence gets initalized to
Nothing. The if statement in Bob's post doesn't assign a value to it if
wk is anything else than 1 or 2 so there is a high potentional for a
NullReferenceException. Bob didn't post the code where the compiler
complains though so hard to tell if there might be a problem. Consider
the following:
Dim wk As Integer = 5
Dim myvar As String
If wk = 1 Then
myvar = "yes"
ElseIf wk = 2 Then
myvar = "no"
End If
myvar = myvar.Trim()
The compiler complains on the last row and if you ignore it you will get
a nice null reference exception when you run it.
/claes
Boo,
Really nice as you want it.
Dim employeecode as integer = 0
dim ammount = 10000
If employeecode = 1 then
salary = ammount * 10
Elseif employeecode = 2 then
salary = ammount * 20
End if
Dim TheSalaryOfBooBoo as integer = salary
It throws no error, but I think it is what you want, I have another opinion
:-)
Cor
"GhostInAK" <gh*******@gmail.comschreef in bericht
news:be**************************@news.microsoft.c om...
Hello Cor Ligthert [MVP],
I disagree with Cor on this point. Initializing a variable at
instantiation is something I really like.
Dim tValue As String
Dim tValue As String = String.Empty
Of the two statements above I prefer the latter. This guarantees that you
will actuially have a string (instead of Nothing).. it avoids the compiler
initialization warning.. and it makes it so you don't have to guess what
the variable holds since you initialize it right off the bat with a value
of your choosing. More than that.. the first statement has an unfinished
feel to it that makes my skin crawl.. like the programmer was lazy and did
a half-ass job.
-Boo
>Bob,
An addition to Herfrieds answer,
It is good investigate these warnings and not to solve them by
intializing with some dumb value as some like to do.
Use values inside the level you need them and don't declare them as
done in the old cobol time in top of a program (this Cobol method is
partially adepted by BASIC people too).
Set option explicit to On and code your program like that.
Cor
"Bob" <sd@qscsqschreef in bericht
news:%2****************@TK2MSFTNGP06.phx.gbl...
>>Hi,
I compiled an application for the first time with no errors but
following
warnings:
1) variable declaration withoit an 'AS':
Dim def()
2) variable 'myvar' is used before it has been assigned a value:
Dim myvar
.....
If wk = 1 Then
myvar = "yes"
ElseIf wk = 2 Then
myvar = "no"
End If
......
3) unused variable: myvar2
Warning 3) is easy to solve: remove it.
Warning 1): is it important to specify (e.g. dim def() as string)?
Can
this cause a run-time error?
Warning 2): is this a problem? Can i leave it like this (i'm sure
'myvar'
will get a value, so no risk of run-time error ...)
Thanks for advice
Bob
Hello Cor Ligthert [MVP],
Well, to my eyes there are four things wrong with your example.. Let's not
forget we're in a discussion about best practices and personal preferences.
First, you forgot (or did not) declare salary and initialize it.
Second, when testing for multiple values in a single variable you MUST ALWAYS,
regarless of your preference in instantiation initializers, account for the
unknown, even if your response to unknown is to throw an error.
Third, you forgot to declare the type of ammount.
Fourth, the constants 1 and 2 do not mean anything to me.. an enum is more
readable.
I also prefer Select Case to ElseIf..So the example becomes:
Public Enum EmployeeCode
Grunt = 0
MiddleManager = 1
End Enum
Dim tEmployeeCode As EmployeeCode = EmployeeCode.Grunt
Dim tAmount As Decimal = 10000
Dim tSalary As Decimal = 0
Dim tTheSalaryOfBooBoo As Decimal = tSalary
Select Case tEmployeeCode
Case EmployeeCode.Grunt
tSalary = tAmount * 10
Case EmployeeCode.MiddleManager
tSalary = tAmount * 20
Case Else
Throw New Execption("DANGER WILL ROBINSON! DANGER! Unrecognized
Employee Code.")
End Select
tTheSalaryOfBooBoo = tSalary
-Boo
Boo,
Really nice as you want it.
Dim employeecode as integer = 0
dim ammount = 10000
If employeecode = 1 then
salary = ammount * 10
Elseif employeecode = 2 then
salary = ammount * 20
End if
Dim TheSalaryOfBooBoo as integer = salary
It throws no error, but I think it is what you want, I have another
opinion
:-)
Cor
"GhostInAK" <gh*******@gmail.comschreef in bericht
news:be**************************@news.microsoft.c om...
>Hello Cor Ligthert [MVP],
I disagree with Cor on this point. Initializing a variable at
instantiation is something I really like.
Dim tValue As String
Dim tValue As String = String.Empty
Of the two statements above I prefer the latter. This guarantees
that you will actuially have a string (instead of Nothing).. it
avoids the compiler initialization warning.. and it makes it so you
don't have to guess what the variable holds since you initialize it
right off the bat with a value of your choosing. More than that..
the first statement has an unfinished feel to it that makes my skin
crawl.. like the programmer was lazy and did a half-ass job.
-Boo
>>Bob,
An addition to Herfrieds answer,
It is good investigate these warnings and not to solve them by
intializing with some dumb value as some like to do.
Use values inside the level you need them and don't declare them as
done in the old cobol time in top of a program (this Cobol method is
partially adepted by BASIC people too).
Set option explicit to On and code your program like that.
Cor
"Bob" <sd@qscsqschreef in bericht
news:%2****************@TK2MSFTNGP06.phx.gbl.. .
Hi,
I compiled an application for the first time with no errors but
following
warnings:
1) variable declaration withoit an 'AS':
Dim def()
2) variable 'myvar' is used before it has been assigned a value:
Dim myvar
.....
If wk = 1 Then
myvar = "yes"
ElseIf wk = 2 Then
myvar = "no"
End If
......
3) unused variable: myvar2
Warning 3) is easy to solve: remove it.
Warning 1): is it important to specify (e.g. dim def() as string)?
Can
this cause a run-time error?
Warning 2): is this a problem? Can i leave it like this (i'm sure
'myvar'
will get a value, so no risk of run-time error ...)
Thanks for advice
Bob
Boo,
I knew that it was wrong, and I assume that you know that I could have done
it right well. It was only meant to show what could happen if you did
initialize and your program was wrong and than nothing was showed. In fact
did you commit that with your corrected code.
Beside that I see not any reason to initialize because it takes only some
instruction extra and that is all, it is nothing more than killing a
warning.
Cor
"GhostInAK" <gh*******@gmail.comschreef in bericht
news:be**************************@news.microsoft.c om...
Hello Cor Ligthert [MVP],
Well, to my eyes there are four things wrong with your example.. Let's not
forget we're in a discussion about best practices and personal
preferences.
First, you forgot (or did not) declare salary and initialize it.
Second, when testing for multiple values in a single variable you MUST
ALWAYS, regarless of your preference in instantiation initializers,
account for the unknown, even if your response to unknown is to throw an
error.
Third, you forgot to declare the type of ammount.
Fourth, the constants 1 and 2 do not mean anything to me.. an enum is more
readable.
I also prefer Select Case to ElseIf..So the example becomes:
Public Enum EmployeeCode
Grunt = 0
MiddleManager = 1
End Enum
Dim tEmployeeCode As EmployeeCode = EmployeeCode.Grunt
Dim tAmount As Decimal = 10000
Dim tSalary As Decimal = 0
Dim tTheSalaryOfBooBoo As Decimal = tSalary
Select Case tEmployeeCode
Case EmployeeCode.Grunt
tSalary = tAmount * 10
Case EmployeeCode.MiddleManager
tSalary = tAmount * 20
Case Else
Throw New Execption("DANGER WILL ROBINSON! DANGER! Unrecognized
Employee Code.")
End Select
tTheSalaryOfBooBoo = tSalary
-Boo
>Boo,
Really nice as you want it.
Dim employeecode as integer = 0
dim ammount = 10000
If employeecode = 1 then
salary = ammount * 10
Elseif employeecode = 2 then
salary = ammount * 20
End if
Dim TheSalaryOfBooBoo as integer = salary
It throws no error, but I think it is what you want, I have another
opinion
:-)
Cor
"GhostInAK" <gh*******@gmail.comschreef in bericht
news:be**************************@news.microsoft. com...
>>Hello Cor Ligthert [MVP],
I disagree with Cor on this point. Initializing a variable at
instantiation is something I really like.
Dim tValue As String
Dim tValue As String = String.Empty
Of the two statements above I prefer the latter. This guarantees
that you will actuially have a string (instead of Nothing).. it
avoids the compiler initialization warning.. and it makes it so you
don't have to guess what the variable holds since you initialize it
right off the bat with a value of your choosing. More than that..
the first statement has an unfinished feel to it that makes my skin
crawl.. like the programmer was lazy and did a half-ass job.
-Boo
Bob,
An addition to Herfrieds answer,
It is good investigate these warnings and not to solve them by
intializing with some dumb value as some like to do.
Use values inside the level you need them and don't declare them as
done in the old cobol time in top of a program (this Cobol method is
partially adepted by BASIC people too).
Set option explicit to On and code your program like that.
Cor
"Bob" <sd@qscsqschreef in bericht
news:%2****************@TK2MSFTNGP06.phx.gbl. ..
Hi,
>
I compiled an application for the first time with no errors but
following
warnings:
1) variable declaration withoit an 'AS':
Dim def()
2) variable 'myvar' is used before it has been assigned a value:
Dim myvar
.....
If wk = 1 Then
myvar = "yes"
ElseIf wk = 2 Then
myvar = "no"
End If
......
3) unused variable: myvar2
Warning 3) is easy to solve: remove it.
Warning 1): is it important to specify (e.g. dim def() as string)?
Can
this cause a run-time error?
Warning 2): is this a problem? Can i leave it like this (i'm sure
'myvar'
will get a value, so no risk of run-time error ...)
Thanks for advice
Bob
This thread has been closed and replies have been disabled. Please start a new discussion. Similar topics
by: John Timbers |
last post by:
I'd like to purchase Visual C# .Net for learning purposes only since it's a
lot cheaper than Visual Studio (note that I'm a very experienced C++
developer). Can someone simply clarify the basic...
|
by: lester |
last post by:
a pre-beginner's question:
what is the pros and cons of .net, compared to ++
I am wondering what can I get if I continue to learn C# after I have learned
C --> C++ --> C# ??
I think there...
|
by: rodchar |
last post by:
Hey all,
I'm trying to understand Master/Detail concepts in VB.NET. If I do a data
adapter fill for both customer and orders from Northwind where should that
dataset live?
What client is...
|
by: Jason Gogela |
last post by:
Does anyone out there know why I should care whether a <span> is nested in a
<p> or vice versa? What is the bennafit of adhering to this standard? It
seems to me that regardless of which way you...
|
by: Tiraman |
last post by:
Hi ,
I am using allot the try catch in my code and the question is
if it is good ?
it will decrease my performance ?
one more question
|
by: zexpe |
last post by:
I have an extremely cpu/data intensive piece of code that makes heavy
use of the following function:
void convertToDouble(const std::string& in, double& out)
{
out = atof(in.c_str());
}
I...
|
by: MP |
last post by:
Greets,
context: vb6/ado/.mdb/jet 4.0 (no access)/sql
beginning learner, first database, planning stages
(I think the underlying question here is whether to normalize or not to
normalize this...
|
by: engwar |
last post by:
Which starter kit or open source project would you consider
well-architected? Or more specifically which has good examples to
showing a newbie how to separate presentation/business logic/data...
|
by: runa2104 |
last post by:
Interview Question
Visit this site it is really good question on C language.
http://techinterviewquestion.blogspot.com/2007/05/c-question.html
|
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:
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: jinu1996 |
last post by:
In today's digital age, having a compelling online presence is paramount for businesses aiming to thrive in a competitive landscape. At the heart of this digital strategy lies an intricately woven...
|
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: 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...
| |
