+1 for C# style properties. I see no downside. Looks like Delphi
properties from 12 years ago. When I went to Java I missed them.. I
was surprised how Java was a step backwards in many ways from Delphi.
And we STILL don't have events and properties 12 years later!
On Feb 6, 11:24 am, joncfoo
I've used that library and simulated up to 40 clients reading and
writing from an sqlite db. Unless moz is doing some thing unusual
sqlite only locks on write operations and the lock handling approach
is to just keep trying until it works.
Best of luck.
On Feb 8, 10:28 am, Marcelo Morales
wrote
Firefox 3 uses sqlite to store cookies. Earlier mozillas used text files.
The Sqlite database contains only one table. The structure is:
moz_cookies (id INTEGER, name TEXT, value TEXT, host TEXT, path
TEXT,expiry INTEGER, lastAccessed INTEGER, isSecure INTEGER,
isHttpOnly INTEGER)
I don't think se
Not convinced myself that this is an acceptable alternative, but:
What if we just bite the bullet and say that use of an IDE (or at
least a /very/ smart syntax highlighter) is so commonplace that they
may be assumed? Then the editor could render properties in italics, or
something. Problem solved
Yes, this is a nice library and I have used it in the past but I will
have to take a closer look. I am not sure it offers what I am after.
I want to examine the a browser's cookies from a Java application.
On Feb 6, 3:42 pm, Van Riper wrote:
> On Fri, Feb 6, 2009 at 9:15 AM, carljmosca wrote:
Not that it matters to your point but I am writing an application, not
an applet.
Still I am aware of the security implications.
Thank you.
> It should NOT be possible to examine browser cookies from an applet.
> It would be a serious security issue. There is no other
> platform-independent re
Jess Holle wrote:
> joncfoo wrote:
>> What's wrong with syntactic sugar and how is it holding it back? The
>> properties that C# sports are simple, concise, and easy on the eyes.
>> Why isn't the Java language picking up at least these basic features?
>>
> What clearly shows in the Tutorial be
joncfoo wrote:
> What's wrong with syntactic sugar and how is it holding it back? The
> properties that C# sports are simple, concise, and easy on the eyes.
> Why isn't the Java language picking up at least these basic features?
>
What clearly shows in the Tutorial below is that C# inherits Micr
As I said, look at perl, joncfoo.
The thinking "It's just syntactic sugar, what harm could it do" isn't
the proper mindset when evaluating new languages. These are the
problems all language changes must face, syntax sugar or no:
1 - complexity
It would be nice if the language spec is grokkable
Been asking that question for a very long time myself, the answers
usually revolve around:
- Denial and lack of understanding/exposure to a component model
(Example:
http://weblogs.java.net/blog/hansmuller/archive/2007/01/property_syntax.html).
- Conservatism and NIH politics (Example:
http://j
10 matches
Mail list logo
