Language:
switch to room list switch to menu My folders
Go to page: First ... 27 28 29 30 [31] 32 33 34 35 ... Last
[#] Fri May 08 2009 07:57:43 EDT from Ford II @ Uncensored

[Reply] [ReplyQuoted] [Headers] [Print]

http://www.theregister.co.uk/2009/05/07/verity_stob_cplusplus/

I had heard about this, but I had forgotten, but alas, I think they're serious.

I like the bit about the most vexing parse.

I knew about the template-space ambiguiuty: if you pass a template to a template, you have to leave a space so the compiler can tell the difference from >>
argh < blargh<int>> isn't cool, but argh <blargh<int> > is.

But apparently there's something that's completely ambiguous, a forward function declaration.

[#] Fri May 15 2009 10:21:03 EDT from IGnatius T Foobar @ Uncensored

[Reply] [ReplyQuoted] [Headers] [Print]

I'll wait for cPlusPlusPlus, it's gotta be even better.
\

[#] Fri May 15 2009 12:17:46 EDT from fleeb @ Uncensored

[Reply] [ReplyQuoted] [Headers] [Print]


They're calling it C++0x or some such nonsense.

[#] Fri May 15 2009 12:34:39 EDT from IGnatius T Foobar @ Uncensored

[Reply] [ReplyQuoted] [Headers] [Print]

I think "C++0x" meant that the "0x" would be replaced by the last two digits of the year the specification is finalized. That would make it "C++09" if it's this year.

"C1x" is supposedly on the way too.

[#] Fri May 15 2009 14:13:25 EDT from fleeb @ Uncensored

[Reply] [ReplyQuoted] [Headers] [Print]


They're updating C now, too?

[#] Fri May 15 2009 14:17:02 EDT from LoanShark @ Uncensored

[Reply] [ReplyQuoted] [Headers] [Print]


where's log00x?

[#] Fri May 15 2009 16:14:10 EDT from Ford II @ Uncensored

[Reply] [ReplyQuoted] [Headers] [Print]

where's log00x?

That's what I was thinking.

[#] Fri May 15 2009 16:18:19 EDT from LoanShark @ Uncensored

[Reply] [ReplyQuoted] [Headers] [Print]


longest running vaporware EVAR.

[#] Fri May 15 2009 17:41:05 EDT from IGnatius T Foobar @ Uncensored

[Reply] [ReplyQuoted] [Headers] [Print]

Nuh uh. Duke Nukem Forever is written in Log00x.

[#] Thu Jun 11 2009 16:02:43 EDT from fleeb @ Uncensored

[Reply] [ReplyQuoted] [Headers] [Print]


http://bennolan.com/?p=82

Some of you might, possibly, remember Ben Nolan as that guy who wrote the behaviour.js library.

[#] Thu Jun 11 2009 16:03:24 EDT from fleeb @ Uncensored

[Reply] [ReplyQuoted] [Headers] [Print]


Oh, and the above link refers to something he wrote regarding C++... something very, very whimsical that folks here should appreciate.

[#] Sun Jun 14 2009 23:28:20 EDT from IGnatius T Foobar @ Uncensored

[Reply] [ReplyQuoted] [Headers] [Print]

Heh. Cute.

[#] Wed Jul 01 2009 13:10:43 EDT from LoanShark @ Uncensored

[Reply] [ReplyQuoted] [Headers] [Print]

Fecking export restrictions... making everyone's life difficult.

Thought I'd spread the word on this one:

-----Original Message-----
From: Tim Orbaker [mailto:tim@orbaker.com]
Sent: Wednesday, July 01, 2009 12:10 PM
To: cryptix-users@lists.sourceforge.net
Subject: [Cryptix-users] Impending certificate expiration

I am using cryptix-jce and cryptix-openpgp in an application. The certificate that signed the cryptix-jce-provider jar expires on 28 Aug 2009.

We will all either need:

1 - A new build, signed with a newer key.
2 - A new JCE implementation that doesn't require signed jars.
3 - A new package to use.

Are others aware of this impending date and what are your plans?

Tim Orbaker

[#] Fri Jul 03 2009 20:17:47 EDT from Ford II @ Uncensored

[Reply] [ReplyQuoted] [Headers] [Print]

I plan on finding out the hard way.

[#] Sat Jul 04 2009 17:14:34 EDT from Ford II @ Uncensored

[Reply] [ReplyQuoted] [Headers] [Print]

I. Win.
for years (pretty much when AT&T stopped me from being able to ssh to my machine at home) I've been toying with the idea of making a connected socket over an http proxy. Corporate firewalls don't let you do ANYTHING, but they let you make http requests. So now I have a way to make a persistent socket over a http proxy.
It needs a little cleaning up and some throttle conhtrol, but I got it to run an ssh session, and once you have ssh, you can tunnel whatever you want. I ran xeyes, it was funny.
Oh I can't wait to take this to work.

You kinda have to be a geek, and you need a machine on the outside you can control, but if you've got that, you can do anything from your corporate desktop as long as you have an http proxy.
Oh, the fun this is going to be.
Please don't douse my flame and tell me somebod's already done this... I don't want to know, I'm just happy I got it working.

[#] Sun Jul 05 2009 05:03:40 EDT from dothebart @ Uncensored

[Reply] [ReplyQuoted] [Headers] [Print]

there also is ssh via DNS which is even more weird.



[#] Sun Jul 05 2009 09:05:30 EDT from Ford II @ Uncensored

[Reply] [ReplyQuoted] [Headers] [Print]

oooh, I like that.
But I wan't tryin to be cool, I was trying to get past our firewall.
I guess if I kept making reqests of MY dns server that could work.

[#] Sun Jul 05 2009 23:06:25 EDT from Peter Pulse @ Uncensored

[Reply] [ReplyQuoted] [Headers] [Print]

So, how did you do it? The proxy doesn't time out??

[#] Mon Jul 06 2009 09:39:28 EDT from Ford II @ Uncensored

[Reply] [ReplyQuoted] [Headers] [Print]

I don't persist connections.
I make a new proxy request every second (or on demand if there's data waiting on the client side. )
The persistence happens on the two daemons. One is on the client attached to ssh for example, and the other is on the server attached to sshd for example.
The two daemons speak to each other through the cgi...


Let's say you run ssh

ssh 127.0.0.1 port 4444 -> daemon#1 listens on port 4444 -> accepts connection ,holds on to socket.
Every second daemon #1 looks for data coming from ssh client. Makes an http request to my cgi over web proxy.
request -> web proxy -> my cgi -> connects to daemon#2 port 6666 -> daemon#2 listens on port6666 for stuff from the cgi.
The first command sent by daemon#1 is "connect" so daemon #2 connects to sshd and holds on to the connection.
The cgi disconnects from port 6666, the cgi goes away, having sent its response back to damon #1.
from then on, the same thing happens, daemon #1 calls cgi with data, cgi sends it to daemon2, daemon2 sends it to sshd connection. daemon 2 then takes any waiting data from sshd connection, returns it as the response to the cgi.
The cgi returns it to the daemon #1 that sends it back to the ssh client.

If either end hangs up, the daemon on that side sends a command to the other saying "my end hung up you can hang up now."
I've only tried it locally on my webserver, I haven't tried it over an actual web proxy over the net yet.
But the test run worked marvelously.

[#] Mon Jul 06 2009 10:08:51 EDT from Peter Pulse @ Uncensored

[Reply] [ReplyQuoted] [Headers] [Print]

Cool, very clever. But the 1 second jumps must be hell when you are doing an interactive terminal or editor.

Go to page: First ... 27 28 29 30 [31] 32 33 34 35 ... Last