Re: Euphoria's identity/philosophy -- Where is the focus?

new topic     » goto parent     » topic index » view thread      » older message » newer message

I think what everyone is referring to in recent comments here is the concept of a software design pattern:

Wikipedia said...

In software engineering, a design pattern is a general reusable solution to a commonly occurring problem within a given context in software design. A design pattern is not a finished design that can be transformed directly into source or machine code. It is a description or template for how to solve a problem that can be used in many different situations. Patterns are formalized best practices that the programmer can use to solve common problems when designing an application or system.

(emphasis mine)

There may be many ways to accomplish the same task, but the community will often converge on a single best practice for solving a single common problem. Those best practices should be reviewed and captured somewhere for others in to reference later. Perhaps this is worth of a Wiki section called "Euphoria Design Patterns" or something like that. These practices, however, are beyond the scope of the language itself.

It is up to the programmer, not the language author, to determine the "best" practice for his task. Hopefully the programmer is following our previously-defined design patterns in his work. It is up to the language author, not the programmer, to ensure that the language can accomplish the task as it is described by the programmer. Hopefully the language author is driven by logic and reason, and not just his own ambition for the language.

-Greg

new topic     » goto parent     » topic index » view thread      » older message » newer message

Search



Quick Links

User menu

Not signed in.

Misc Menu