I imagine that much the same applies to linux.
--
You received this message because you are subscribed to the Google Groups "The
Java Posse" group.
To post to this group, send email to javapo...@googlegroups.com.
To unsubscribe from this group, send email to
javaposse+unsubscr...@googlegroups.c
perhaps I over-estimate the typical windows user. I apologize to all
windows users.
pretty funny that "cd c:/windows" works but "dir c:/windows" doesn't
On Sat, Jan 1, 2011 at 6:21 PM, Ricky Clarkson wrote:
> Hey, the path your program output didn't make any sense, look:
>
> dir c:/windows
>
Hey, the path your program output didn't make any sense, look:
dir c:/windows
Parameter format not correct - "windows".
I think you meant to put a \ not a / , I bet it was that Jarva again.
On Sun, Jan 2, 2011 at 12:54 AM, phil swenson wrote:
> well put.
>
> although I don't think a windows us
well put.
although I don't think a windows user is going to be confused by c:/foo/bar
On Fri, Dec 31, 2010 at 3:18 PM, Reinier Zwitserloot wrote:
> File.separator is intended only for rendering paths to the user. A windows
> user is going to be very confused by C:/foo/bar.
> It serves absolutel
Files are so passé anyway... to the cloud!
#sarcasm
--
You received this message because you are subscribed to the Google Groups "The
Java Posse" group.
To post to this group, send email to javapo...@googlegroups.com.
To unsubscribe from this group, send email to
javaposse+unsubscr...@googlegr
In this example you forgot:
File temp4 = new File("temp", "hello");
Mark
--
"Great artists are extremely selfish and arrogant things" — Steven Wilson,
Porcupine Tree
On Thu, Dec 30, 2010 at 8:19 PM, Augusto Sellhorn <
augusto.sellh...@gmail.com> wrote:
>File temp = new File
File.separator is intended only for rendering paths to the user. A windows
user is going to be very confused by C:/foo/bar.
It serves absolutely no purpose anywhere else, and I consider it a bug that
this concept is not properly documented in the appopriate java doc.
Feel free to mark down any
phil swenson
> To: javaposse@googlegroups.com
> Sent: Wed, December 29, 2010 6:50:12 PM
> Subject: Re: [The Java Posse] Re: File.separator question
>
> IMO if you agree that "/" works in all relevant cases, then using a
> new constant doesn't make any more sense tha
Check your code. If Letter.P == 'P' and so on, then
Letter.P + Letter.H + Letter.I + Letter.L == 'ĭ'
Alexey
From: phil swenson
To: javaposse@googlegroups.com
Sent: Wed, December 29, 2010 6:50:12 PM
Subject: Re: [The Java Posse] Re: Fil
File.separator is portable, / is not, ugly or not always opt for the
more portable option.
For example, this code;
---
import java.io.*;
public class FileSeparator
{
public static void main(String[] argv)
One thing I will say, it'll *really* annoy anyone trying to do any kind of
text processing against a log file that contains the "wrong" separator...
Use / by all means, but replace it with the system default before using the
path. In Java, I tend to write a small normalisePath function or some suc
IMO if you agree that "/" works in all relevant cases, then using a
new constant doesn't make any more sense than saying a comma separated
list should be build using a "Punctuation.COMMA" constant. Or my name
should start with a "Letter.P" constant.
Just my opinion,
Letter.P + Letter.H + Letter.
I think you'd want to use "File.separator" instead of hard coding "/" for the
same reasons constants are better than hard-coded values in general.
It captures the semantic context of the constant value, for one thing. It's
clear that you intend to use a file separator character in that context.
Yeah, that's my experience. You might need it if you are building
paths for display or whatever. There might be some other weird
conditions where you might need it (edit or building existing paths).
But for something simple like new File("./path/file"); I can't see why
you would need the File.sep
14 matches
Mail list logo
