Is the LISA language object oriented? - oop

I came across some code in the LISA language while working on an ARM based project. The code look much similar like a mix of VHDL and C++. I tried to google out to get an introduction to the language. I couldn't find much help.If some one has good experience in LISA please guide in the approach to be taken in understanding the language design or basically what will be a good starting point to master it .
I got a link to the university where this has been found
https://www.ice.rwth-aachen.de/research/tools-projects/lisa/lisa/
But on understanding this as a language(basically how to code in it) the information provided there is insufficient I feel . We don't even have a tag for this in SO!!

To answer your question -
"LISA is a descriptive programming language and not object oriented"
You can go through this Paper - LISA
Machine Description Language and
Generic Machine Model for
HWSW CoDesign
for more details. The language has not been yet standardized by IEEE and ISO yet and is in its enhancement phase.

Related

In which language was Thimbleweed Park game made>

I am a game developer and I wanted to know in which language was thimbleweed park made? Was it c# or c++ or something else? I searched on google but there is no relevant information about it.
According to Wikipedia:
Gilbert had already started to look for adventure game engines in August 2014, but because of his experience of always wanting to modify engines to do exactly what he wants from them, he decided it would be easier to create his own engine.
He already had a 2D graphics engine written in C/C++ that he had used for his non-adventure games The Big Big Castle! and Scurvy Scallywags, which he decided to use for Thimbleweed Park; SDL was used for handling window creation and input, while Gilbert's own code was used for rendering the graphics. The only other thing that was needed for the engine was a scripting language; Gilbert had looked at Lua, and while he considered it "easy to integrate and highly optimized", he disliked its syntax. He considered making his own scripting language, but due to time concerns, he chose the language Squirrel instead.

Recommendations about a book or tutorial to learn about labview

I would like to find the best tuttorial or free pdf book. To learn Labview, I am new to this program. If I were in Spanish, it would be better if there was no problem.
I am working with Richard Jennings on the fifth edition of the book "LabVIEW Graphical Programming". It is scheduled to release later on this year.
In the meantime, check out the LabVIEW Wiki at https://labviewwiki.org/wiki/Home
You can ask questions and find examples at the LAVA and NI forums at
https://lavag.org/
https://forums.ni.com/t5/Discussion-Forums/ct-p/discussion-forums
You could also look for a LabVIEW User Group in a Spanish speaking community. They might have more information in Spanish. Check out:
https://forums.ni.com/t5/User-Groups/ct-p/user-groups
It's an old one but a good one:
LabVIEW for Everyone: Graphical Programming Made Easy and Fun
It brings you from zero to hero with most of the key concepts along the way to become a Certified LabVIEW Developer. Note, newer architectures are not included but it is perfect for a beginner.
You can read it for free from Reilly for 10 days: https://www.oreilly.com/library/view/labview-for-everyone/0131856723/

What are the most valuable parts of Computer Science studies for Cocoa developers?

What are the most valuable parts of Computer Science studies for Cocoa developers?
Another way I might word this question is:
If I’m not going to go to school for Computer Science but want to be a developer working primarily with Cocoa, what are the things I should make sure I learn that I otherwise might miss by being self-taught, and be worse off for it.
Update: Replaced the term "professional Cocoa developer" with "developer primarily working with Cocoa", in hopes that the intent of my question is somehow clearer.
To be clear, I've been working with Cocoa for two years and am comfortable with Objective-C and the Cocoa frameworks, as well as Cocoa design patterns and the developer toolset, and thus am for the most part fluent with the Mac and iPhone platforms. But I have wondered whether I'm missing important CS or SE elements due to being self taught/no formal training, and not coming from other languages or platforms.
This question is for Cocoa developers.
There are many, but things that come to mind imediatly
-Design Patterns (the Cocoa framework relies on many Design Patterns, if you follow them it will make your life very easy, most obvious example is MVC)
-Algorithms and Data structures(this applies to any framework really)
-Memory Management (No garbage collection on the iphone!)
I would question whether there's really such a thing as a "professional Cocoa developer" (from a philosophical standpoint), or if you would want to be one. There's "professional developer", who may work with Cocoa primarily. A professional developer is language-agnostic and as such has a solid career ahead of him/her. A language- or platform-specific hacker has very limited usefulness.
The question to ask is do you want to be a developer or not? If there aren't any good Cocoa jobs available at the moment, or Cocoa is replaced by something newer and better and very different, a professional developer changes gears and follows. Are you OK with that?
If so, a computer science degree definitely cannot hurt. If not, you should probably not put all your eggs in the Cocoa basket and pursue a non-CS degree.
In addition to what's been pointed out already, I highly recommend reading "The Pragmatic Programmer". It contains a wealth of information on how to write software, how to manage projects, and how to develop your career, advice that goes well beyond the documentation you look at every day in Xcode. Some of the topics they cover are ones that you might have been exposed to during a standard computer science degree.
"Professional" is a relative term.. but anyways, this is what i had to go through so that i could easily learn a new language anytime i want and also master it:
started by learning a simple console language (pascal or c++, but i consider pascal being simpler than c/c++), then learned another language just to see if i can do it (c++)
i learned a lot of algorithms and data structures, until i was able to recreate them and even create my own
i moved to a visual approach on programming with Visual Basic 6 (another simple one to start with), and tried to copy lots of apps just to see if i can do it
i learned about Object-Oriented Programming and finished by mastering it
from this step on, learning a new language was like a hobby, like playing!
then i wanted to learn some different topics, like design patterns, multithreading, and so on..
moved from windows to mac, and started learning objective-c: because i already knew lots of languages, it took me 5 days to learn objective-c, and yes, i took breaks like any human being :P
after i learned obj-c, i now had to learn cocoa... this one took me a lot of time to learn, and i still don't know it all.. but i do know most of it :D
What are the most valuable parts of Computer Science studies for Cocoa developers?
Learn that it's important to understand the differences between languages, not learning a particular language.
Are you writing numerical method solvers with a Cocoa frontend? You'll want to take numerical methods. Writing a 3-D plugin with a Cocoa UI? Better learn about Catmull-Rom splines.
A good understanding of computer graphics is required if you want to make some good looking animations :)

Finding language designers and programmers

I'd like to create a new and open sourced language.
Since it's really rare to find programmers that actually dealt with compiler theory I need some advice.
How would you make a person interested in your open source project?
How do you bring him to a position where he wants to contribute?
Is there a special place where I can find those pepole (except sourceforge.net)?
It will be very hard to get people interested in your project. History has shown that 99% (at a conservative estimate) of new programming languages are only ever used by their designer. So if you do it, do it for love and don't expect much if any outside interest.
You may want to spend some time lurking on sites like, say, Lambda The Ultimate and reading up on theory of programming languages, compiler design, etc. I've heard that Essentials of Programming Languages by Friedman et al is a good intro text for the former, while you can't go wrong with the "Dragon Book" for the latter (whose official title escapes me at the moment... by Aho et al though).
take a look at Haskell (and its supporting community)
http://www.haskell.org/
I've used Haskell to model a small OO programming language in grad school and it seemed to be a common tool used in the Academia for designing programming language
BTW, this doesn't answer your questions but these two Microsoft / Codeplx projects both sparked my interest as possible starting points for creating a new language:
Dynamic Language Runtime
Common Compiler Infrastructure

I need an accurate, comprehensive and idiot-proof OOD tutorial to help me avoid Global variables in C#

Can anyone point me in the direction of a very good online OO Design (and Programming) tutorial or resource ?
I appear to have badly designed a small AP in C# and now want to sort it out before I go any further and frustrate myself even more.
I did try to do it quickly and only went over a small and insignificant (now I realise) tutorial on OODP and C# and classes etc and not given it the importance, and time, its obviously needs.
Actually, a good C# tutorial would be helpful too - I only read the C# Programming guide (Public Beta Release), a very old book - 2000/1.
More haste less speed etc. doh
Thanks, George.
I have pointed people to both of these resources before, they are a little basic but they over some good high level overviews:
Learning C# and OOP
C# an Object Oriented Introduction
A lot depends on your skill level and how you design programs in general (your background etc).
It will come with experience. One of my favorite ways to learn is to have a senior coder with 20+ years of experience to tear my code apart. No pain - no gain. The book knowledge goes into one eye and comes out of the other ... Post some code here, damn it!