Rumores y novedad en el nuevo Delphi

[Jure]

Leyendo los blogs de Michael Swindell y Danny Thorpe me encontre con esto:


Some rumors I read in the NGs and blogs last night:

Rumor: "I hope Diamondback is more than just Delphi 7 and Delphi 8 combined"
Fact: Way more. If it were just 7 & 8 combined, we'd just call it "Garter Snake"

Rumor: "Diamondback will be two IDEs one for Win32 and one for .NET"
Fact: Diamondback will be a single IDE :o)

Rumor: "Diamondback will include ECO for ASP.NET, Refactoring, and Unit Testing"
Fact: Thats just scratching the surface...

Rumor: "Danny, JohnK, Corbin, Jim and Allen are hotshots"
Fact: Heck ya

Rumor: "DiamondBack will be the best development tool in the world"
Fact: Alright, who broke their NDA? Someone call security please.

Si quieren leer la nota completa puden hacer click aqui:

http://homepages.borland.com/mswindell/2004/08/diamondback-rumors.html#comments

Una nueva sintaxis para un ciclo, el "for..in" que se incluira en el nuevo Delphi:

http://homepages.borland.com/dthorpe/blog/delphi/2004_08_01_archive.php#109211211041479238

Jure.

[marto]

Wop!

Muy interesante!!!!!
Por cierto, en los comentarios del blog, hacen referencia a "kitchen sink" como la panacea... ¿alguien sabe qué leches es?

[__hector]

Excelente!! Tambien incluyeron una clausula foreach :D

Y pensar que hace poco lo habia mencionado como parte de D8, creo que en este hilo:

http://www.clubdelphi.com/foros/showthread.php?t=12933&highlight=foreach

[Tony_G]

Os dejo el enlace de la noticia.

http://www.lemanix.com/nick/archive/2004/08/19/1118.aspx

Seguramente tendremos que esperar hasta la BorCon de Septiembre para aclarar las noticias que se leen.

Saludos.

[marcoszorrilla]

Aunque su significado es el fregadero de la cocina. Y también:
kitchen sink drama
tipo de drama que refleja la vida cotidiana de la clase obrera de manera realista.



If One Is Better, Ten Must Be The Best!





While that rant may seem overly long, it sets the stage for this language I'm putting together as kind of another INTERCAL. My impression of INTERCAL was that the designers intended to make fun of the ranting fools pushing Structured Programming (again, without any proof that it was superior). They took all the purported features and turned them on their head, creating a language that was nearly impossible to understand and work with.

With KitchenSink, I'm going to attempt to combine all of the features that language purists claim will make programming better. I figure, if one paradigm is better, then why not include them all! This language will be the best language in the world if you go by how language nuts (i.e. people who think the language and platform are married) rate the latest programming languages. I am going to try to make the language as simple as possible, but in the end, I believe it will be hopelessly useless, and only a novelty. Then again, I may hit onto something and actually make the best language in the world! (yeah, alright)

Here's the short list of the super cool paradigms I'm gonna have in KitchenSink:

Object-Oriented Programming Can't have a language without being a slave to the objects. Even better, my object design will be based on exemplars rather than class structured (another popular academia thingy). That's where you don't define your ontology, but rather just say, "this thing is like that thing with these differences". Functional Programming Functions will be first class objects, will have closures, and you'll be encouraged to make them like crazy even if they don't help the design one bit. Concatenative Programming This latest and greatest language feature--as promoted in Forth (http://www.forth.org/), Onyx (http://www.gnu.org/directory/Software_development/prog/other/onyx.html), Joy (http://www.latrobe.edu.au/philosophy/phimvt/joy.html), and PostScript (http://directory.google.com/Top/Computers/Programming/Languages/Postscript/?tc=1)--creates some wonderfully cryptic programs--and you know how conciseness is next to godliness with math junkies. Who cares if nobody can read it without a diagram of a massive complicated stack flow! It's concise dammit! Templates and Aspect-Oriented Programming Damn, some zealots have proclaimed that "Any language with a pre-processor is broken." Rather than admit that meta-programming is really useful for creating generic components, we'll just recast the pre-processor as "an Aspect-Oriented Compiler", and start calling macros "templates". Structured Programming How could you possibly have any language that wasn't also structured!? Heaven forbid you should create a nice interaction based language like Smalltalk. Nope, it has to be a lock step algorithm or it's not "provable". Logical Proofs and Design By Contract It doesn't matter that Design by Contract has been "proven" (through logic though) to be equivalent to Clean Room logical proofs. It doesn't matter that a logic proof doesn't prevent bugs during runtime. All that matters is that I make software development so difficult that only a trained math genius could ever write a piece of software. That will keep all those pesky H1-B visa carriers out of the business. Full Set Manipulation Operators Hey, everything in a computer is just a set of some kind. Who needs easy to use indexing that follows what everyone was taught in highschool algebra? Let's do what R, Haskell, and now Python have done by making cryptic indexing possible. Tail Recursion Hey, we've got functional programming, but damn making those stacks is really slow. What's that? Why not just introduce that highly usefull concept of "iteration"? Tisk-tisk. That's not very purist of you. Are you sure you're a member of the inner circle? I could have sworn that iteration was a forbidden word in the functional religion. We call that "tail recursion" here. Maybe you should go to the end of the line. Lots and Lots of Idiotic Silly Operators (LLISO) Programming's all about problem solving, and nothing is more fun than reading tons of symbols that, when combined, must be carefully taken apart to understand what's really going on. That really makes the language a wonderful puzzle that needs to be solved (because, as an academic, I don't really need to be solving puzzles with the language, I want to solve them in the language). Even better is when these symbols are the inverse of what everyone else is familiar with using. The main advantage of this is that I can force the user to adopt symbols and structuring constraints which makes my compiler design so much easier. Who needs expressiveness when you have a massive Perceived I.Q. booster like Lisp Parentheses and wonderful stuff like CADR, CDDR, CADDR, and CDDRDDADR!? Hey, that reminds me, most programmers can't type, so let's save keystrokes at every turn and use acronyms and abrvt. kywrds......
Este es el enlace de donde lo he sacado.

http://www.zedshaw.com/writings/kitchensink/

Un Saludo.

[KORN]

Para la proxima si no es mucho inconveniente para ti, traduce el texto.

Que no entendi ni papa.




Saludos

[marcoszorrilla]

Inconveniente no es pero como ya eran las 23h, yo creo que no está nada mal haber encontrado un texto en el que se emplee dicho giro aplicado a la informática.


En cuanto a lo que dices de "papa" no me extraña que no lo entendieras, ya que esta palabra referida al ancestro masculino no figura en el texto.


JaJa.

Un Saludo.

[vic_ia]

hola...
En cuanto a lo que dices de "papa" no me extraña que no lo entendieras, ya que esta palabra referida al ancestro masculino no figura en el texto.
.... bueno cabe aclarar que no se refiere a papá... :p

saludos....

[marcoszorrilla]

obviamente, era un juego de palabras, comprendo la expresión no entender ni papa.

Un Saludo.