Last update April 26, 2010

Bruno Medeiros



Bio

I'm Bruno Medeiros, age 23, a MSc. Computer Science/Engineering student at IST, Lisbon, Portugal.

I am (besides D) knowledgeable in C, C++, Java, C#, and a bit of LISP. I have student-level development experience. My area of interest within CS is game and 3D/multimedia application development, and that is why I got involved with D: A "systems" language like C++ is needed, but C++ is a horrible, outdated mess of a language.

Projects

Working on an Eclipse based D IDE, started as a college thesis project: Mmrnmhrm.

Some other non-D projects: http://web.ist.utl.pt/~bruno.d.o.medeiros/website/projects.html

Bugs

My Bugs at D Bugzilla

D Peeves and Stuff

"Certain aspects of D are a pathway to many abilities some consider to be... unnatural." ...

Design Issues in D I'm keeping track of. (Updated: Aug 2008)

Implicit/Property Function Call (aka omittable parenthesis) http://www.digitalmars.com/d/archives/digitalmars/D/Omittable_parens_is_an_evil_73881.html

Inheriting Constructors

Make null arrays different than empty arrays: Proper Bools: Bools are better now, but there is still some problems. Like, currently, the following expression evaluates to false: 
if( true == 2 ) writeln("THEN"); // The if expression evaluates to false :(
That's bad, a mere obsolescence from C. Either convert ints to bools and not the other way around, or better yet, don't have implicit conversion between numerics and booleans.

signed-unsigned conversions and crappy C-legacy crap:

Example: news://news.digitalmars.com:119/eve2j4$29ul$1@digitalmars.com TBD

Template specialization rules and alias parameters: [NOTDISCUSSED]

private issues: Overriding hides overloads (like C++): A Copy Operator: Is Type Expression trickyness:

When using is expressions type comparisons, such as : 

is(typeof(foo) == Bar)
there will be no compilation errors if there is a semantic error in the expression (like an non-existant variable). Instead, the is expression will also evaluate to false. This is annoying and error-prone, but the developer can't easily distinguish typo-like errors and the valid cases where the is expression should evaluate to false (when the semantic evaluation is ok, but the types don't match).

Nested /* */ Comments: (a small change) [??] (Mar06)

Ctors as regular functions:
    • TODO

Different Cast syntax: Operator/Expression evaluation order

Resolved Design issues

Object.oqEquals returns int and not bool: [FIXED at last]

Static arrays as value types: [FIXED: DMD 2.011 (2008-03)] 
 For time has imprisoned us 
 In the order of our years 
 In the discipline of our ways

FrontPage | News | TestPage | MessageBoard | Search | Contributors | Folders | Index | Help | Preferences | Edit

Edit text of this page (date of last change: April 26, 2010 15:25 (diff))