Thank you for the comments Martin and Stefan. I may try posting this
question on a Java programming forum, but I always like to check here
first.
Martin: I do not know if this error is unique to the Eclipse Compiler.
I haven't compiled it from the command line, so I don't know if this
is an Eclips
RJ, sorry you're having such a frustrating time. I'm sure there's much
better ways the GML I/O support could have been designed - it was done
in a hurry, to meet a pretty specific use case. There may also be bugs
in the codebase, which is possibly what you're running into.
However, until som
Hi,
I believe I can be classified as a power user of number of commercial and open
source GIS software. Though I do not believe I can ever write a working input
or output template. I have tried with poor success. But perhaps it is
impossible to make it more user friendly?
The use cases I have h
Sunburned Surveyor schrieb:
> If I undertstand your suggestion correctly, then the technique you
> suggest doesn't work, at least not with the Eclipse compiler. If you
> declare the variable being returned before the try/catch statements,
> but set the value within the try statement, the Eclipse
The compiler is your friend... just keep it happy. While this little
situation seems like an anti-pattern, it's not hurting anything, so I
just code in this style and don't worry about it.
Is this just an error with Eclipse, or does javac give the same error?
I think this may just be an artif
If I undertstand your suggestion correctly, then the technique you
suggest doesn't work, at least not with the Eclipse compiler. If you
declare the variable being returned before the try/catch statements,
but set the value within the try statement, the Eclipse compiler
complains that you could be r
mhm.. I don't realy get why you put the first return into the try case?
why should one return within a function and not at the end of a method?
(i.e. i have never seen this in java code)
instead declear a new method variable and set their value within try{}
and/or catch{} and return this variable
I've got a quick question about the best way to handle return values
in Java methods with a try/catch statement. Consider, as an example,
the following method:
public static SurveyorsAngle getSupplementaryAngle(SurveyorsAngle argAngle)
{
try
{
SurveyorsAngle halfRevolution = new
I have handpicked a set of items to complete for our next official
release of OpenJUMP. I will keep an updated list of these items on the
JPP wiki. When work is complete I will update the list on the OpenJUMP
wiki.
http://thejumppilotproject.pbwiki.com/The-Sunburned-Surveyor%27s-Task-List
I have
Thank you for all of the information Stefan. I will look over the todo
list again and will select the things I would like to tackle. I'll
post the list for others to review if they wish, with my first set of
questions.
The Sunburned Surveyor
On Jan 29, 2008 8:36 AM, Stefan Steiniger <[EMAIL PROTE
Here's an extract from the JUMP User Guide:
APPENDIX: GML INPUT & OUTPUT TEMPLATES
To read a general GML file, JUMP makes use of a mapping file called a
GML input
template. This template specifies how the contents of the GML file are
mapped to a JUMP
features. Similarly, when saving a GML file,
If I provide the orignal doc from JUMP, is there anyone who can make
available in one of these places? I'll also provide it in an email in
case that's helpful.
Stefan Steiniger wrote:
> Hei Martin,
>
> for now we only have the tutorial by Uwe and the online-doc setup by
> Peppe (i.e. our wiki:
>
> I skimmed over the list this morning, and it seems like we may have
> addressed some of the items on this list already. If you guys could
> take a look and let me know if you've completed some of the tasks I
> will update the list.
I did not found any additional item that I have solved
> Af
13 matches
Mail list logo
