Talk:LPC (programming language)

This article is outdated and incorrect. It needs to be rewritten.

:What do you consider outdated and incorrect on this page. And then we can see

:about rewritting it.

Maybe we should start a MudOS section for specific mudos driver compiling issues?

In addition, this lpc thing should maybe mention Efuns and Simul_efuns. Efuns are C compiled code that you can call within lpc, they run fast as C. The Simul_efuns are lpc that can be called anywhere in the mud code, just like efuns but run same speed as LPC. Our mud, Daybreak Ridge used a ton of Simul_efuns.

-James "Parnell" P.

FFF

Section on LPC function types added.

Chaos5023 15:53, 11 May 2007 (UTC)Chaos5023

This article does not include LDmud variations for particular calls and data types. For example, LDmud now has a struct data type as well, and uses clone_object() instead of new() for instantiating a clone.

-Dennis VanHoey —Preceding unsigned comment added by 76.112.46.222 (talk) 21:03, 22 October 2007 (UTC)

I've made some userboxes for LPC coders and LPMud admins. Chaos5023 16:38, 25 July 2007 (UTC)

:... and have recently updated them to be considerably more appealing. —chaos5023 (talk) 04:29, 11 July 2011 (UTC)

Python programming language → Python (programming language)

– Conformance with WP naming conventions Cybercobra

{{Wikipedia talk:WikiProject Programming languages/Renaming poll}}

There are a lot of details about language features here (data types etc), spanning more than 50% of the article. These should be summarised into a paragraph or two. Technical details about the language etc should be covered in the specification of the language external to Wikipedia. —Preceding unsigned comment added by 203.214.158.105 (talk) 09:16, 9 April 2010 (UTC)

:If you look at the details in question, you'll see that a lot of them are point-by-point comparison of different LPC variants, which a specification cannot provide. Of course, LPC being an implementation-defined language, you're not going to find a specification anyway. —chaos5023 (talk) 09:26, 9 April 2010 (UTC)

Third part is wrong.

Rather than rewriting it I post this comment here. So here goes: in LPC you can declare functions public, protected or private. Public are as noted below accessible from any point, protected only inside the same blueprint (inherit stack) while private only accessible from functions (methods) inside the same file. You *can* access variables externally, but it is not ment to be as such.

Further more, 64bit is now stable. I haven't heard comments about 64bit compilations being unstable, I've used it for years and many muds has.

Probably a lot more work in need to be done for this wiki, it is very outdated.

Sincerely, Silbago of Final Realms. — Preceding unsigned comment added by 84.215.70.184 (talk) 23:58, 12 August 2012 (UTC)

The article could need a history. When was LPC created? Since Felix is still alive perhaps he can answer that. Right now the article does not mention when LPC was created. 2A02:8388:1641:4700:BE5F:F4FF:FECD:7CB2 (talk) 13:30, 11 May 2017 (UTC)

Hello fellow Wikipedians,

I have just modified one external link on LPC (programming language). Please take a moment to review my edit. If you have any questions, or need the bot to ignore the links, or the page altogether, please visit this simple FaQ for additional information. I made the following changes:

• Added archive https://web.archive.org/web/20100204062426/http://pike.ida.liu.se/about/pike/history.xml to http://pike.ida.liu.se/about/pike/history.xml

When you have finished reviewing my changes, you may follow the instructions on the template below to fix any issues with the URLs.

{{sourcecheck|checked=false|needhelp=}}

Cheers.—InternetArchiveBot (Report bug) 14:47, 14 December 2017 (UTC)