Welcome to Omgili,
Omgili ( Oh My God I Love It ;) is a search engine for discussions. With Omgili you can find answers and solutions, debates, discussions, personal experiences, opinions and more... To learn more about Omgili click here.
This is a complete preview of the discussion as it was indexed by Omgili crawlers. Use this preview if the original discussion is unavailable.
Click here to view the original discussion.
 |
|
 |
|
oFear The Fear & Phobia Forum • Rant about - Computers and game consoles
A lot of this is boring studio speak, but I just want to get it out of my system.
I have been working on a song.{I do comedy hip hop} Last night I finished recording the 3rd verse.
I have to transfer it from my digital recorder, to my computer.
Then I have to cut it into sections and line it up, so it's on beat.
Then I have to mix,master,dehiss, set volume levels etc etc....
Today my Ac adapter on my digital recorder was broken, so I had to use batteries.
When I changed the batteries and turned it on, the card for some reason came un-formatted...So I had to reformat and lost everything on there{including what I had last night and some beats for upcoming songs}....It gets worse
So anyway...I put the finishing touches on my recording and transferred it onto my computer studio software.
Then I finish everything and get ready to upload it, and the screen goes white!!
Computer froze 10 hours of work....gone I know I should have stopped and saved a few times, but I got so caught up in what I was doing, that didnt happen!!!
Had my adapter not been broken, I could have at least not had to record the verse over....but of course..like the title says...this is a conspiracy!!
I had this happen just two songs ago too...just not quite this bad..{I only lost 4 hours of work last time!!!}
Anyway, Im going to go find a new hobby like seeing if computer and recording equipment can float{BRB- Im going down by the lake!!}
livid,irate,flabbergasted,peeved,discombobulated,rattled,vexed,stressed,
bugging out, fuming, angry!
|
|
 |
|
 |
|
|
|
|
Oh thats all so crazy Brent Technology eh, who needs it?
Life was so much simpler before it this hi tech equipment came along im sure.
Many times I have wanted to throw my pc from the 20th floor window when things have gone wrong.
I think you should take a step back and get away from all your work and come back and start again when things have calmed down a little.
Hope you feel better soon.
|
|
|
|
|
|
|
|
|
You make a very valid point.
I thought the underlying intention of technology was to make life easier!!!
HA!
Thanks for the pep talk though, and I was able to reassign my frustrated energy into work energy and got it redone in record time!
BTW- I was already over it by the time I said discombobulated in the original post!
What a fun word to say
|
|
|
|
|
|
|
|
|
I too suffer from the problem known as "Come Hell or high water, nothing will make me save my work before it is completely and utterly finished!"
|
|
|
|
|
|
|
|
|
I'm sure almost everyone has been in that situation before.
I guess that's just something we all have to deal with.
One solution is putting a note up in front of the computer: "Save!!!!" LOL
|
|
|
|
|
|
|
|
|
Unfortunately it doesnt seem to matter what you tell people or how many times because nobody backs up enough.
When I was building and repairing pc's a few years back I so often see sad faces when I asked them did you back up??!!!
I guess we all learn from are mistakes eventually.
|
|
|
|
|
|
|
|
|
Well you are right.
I've been in situation where I would lose important information due to not saving in time, that's when I tell myself next time I should save every minute.
But it never happens lol.
|
|
|
|
|
|
|
|
|
...I think that it would be a bit of a waste posting a rant about assembler syntax and the pascal programming language here...
|
|
|
|
|
|
|
|
|
Just a bit yeah I have no idea what you just said But rant away and I'll pretend to know
|
|
|
|
|
|
|
|
|
Yeah that Pascal has got a lot to answer for
|
|
|
|
|
|
|
|
|
You would of thought he could of assembled his syntax a little better considering how important it is
|
|
|
|
|
|
|
|
|
... I'm so lost and confused.
You guys are just too smart for me!
|
|
|
|
|
|
|
|
|
Just for you girls:
Pascal is a structured imperative computer programming language, developed in 1970 by Niklaus Wirth as a language particularly suitable for structured programming.
A derivative known as Object Pascal was designed for object oriented programming.
History
Pascal is based on the ALGOL programming language and named in honor of mathematician and philosopher Blaise Pascal.
Wirth subsequently developed Modula-2 and Oberon, languages similar to Pascal.
Initially, Pascal was a language intended to teach students structured programming, and generations of students have "cut their teeth" on Pascal as an introductory language in undergraduate courses.
Variants of Pascal are still widely used today, for example Free Pascal can be used in both 32 and 64 bit formats, and all types of Pascal programs can be used for both education and software development.
Parts of the original Macintosh operating system were hand-translated into Motorola 68000 assembly language from the Pascal code used in the Apple Lisa, and it was the primary high-level language used for development in the early years of the Mac.
In addition, the popular typesetting system TeX was written by Donald E.
Knuth in WEB, the original literate programming system using Pascal.
Implementions
The first Pascal compiler was designed in Zurich for the CDC 6000 series mainframe computer family.
Niklaus Wirth reports that a first attempt to implement it in Fortran in 1969 was unsuccessful due to Fortran's inadequacy to express complex data structures.
The second attempt was formulated in the Pascal language itself and was operational by mid-1970.
Many Pascal compilers since have been similarly self-hosting, that is, the compiler is itself written in Pascal, and the compiler is usually capable of recompiling itself when new features are added to the language, or when the compiler is to be ported to a new environment.
The GNU Pascal compiler is one notable exception, being written in C.
The first successful port of the CDC Pascal compiler to another mainframe was completed by Welsh and Quinn at the Queen's University of Belfast in 1972.
The target was the ICL 1900 computer.
The first Pascal compiler written in North America was constructed at the University of Illinois under Donald B.
Gillies for the PDP-11 and generated native machine code.
In order to rapidly propagate the language, a compiler "porting kit" was created in Zurich that included a compiler that generated code for a "virtual" stack machine (i.e.
Code that lends itself to reasonably efficient interpretation), along with an interpreter for that code - the p-code system.
Although the p-code was primarily intended to be compiled into true machine code, at least one system, the notable UCSD implementation, utilized it to create the interpretive UCSD p-System.
The P-system compilers were termed P1-P4, with P1 being the first version, and P4 being the last.
A version of the P4 compiler, which created native binaries, was released for the IBM System/370 mainframe computer by the Australian Atomic Energy Commission;
It was called the "AAEC Pascal Compiler" after the abbreviation of the name of the Commission.
A version of P4 from 1975-6 (based on its internal code, it probably should be called "P5") including source and binaries for the compiler and run-time library files for the PDP-10 mainframe may be downloaded from this link.
In the early 1980s, Watcom Pascal was developed, also for the IBM System 370.
IP Pascal was an implementation of the Pascal programming language using Micropolis DOS, but was moved rapidly to CP/M running on the Z80.
In the early 1980s, UCSD Pascal was ported to the Apple II and Apple III computers to provide a structured alternative to the BASIC interpreters that came with the machines.
Apple Computer created its own Lisa Pascal for the Lisa Workshop in 1982 and ported this compiler to the Apple Macintosh and MPW in 1985.
In 1985 Larry Tesler, in consultation with Niklaus Wirth, defined Object Pascal and these extensions were incorporated in both the Lisa Pascal and Mac Pascal compilers.
In the 1980s Anders Hejlsberg wrote the Blue Label Pascal compiler for the Nascom-2.
A reimplementation of this compiler for the IBM PC was marketed under the names Compas Pascal and PolyPascal before it was acquired by Borland.
Renamed to Turbo Pascal it became hugely popular, thanks in part to an aggressive pricing strategy and in part to having one of the first full-screen Integrated development environments.
Additionally, it was written and highly optimized entirely in assembly language, making it smaller and faster than much of the competition.
In 1986 Anders ported Turbo Pascal to the Macintosh and incorporated Apple's Object Pascal extensions into Turbo Pascal.
These extensions were then added back into the PC version of Turbo Pascal for version 5.5.
The inexpensive Borland compiler had a large influence on the Pascal community that began concentrating mainly on the IBM PC in the late 1980s.
Many PC hobbyists in search of a structured replacement for BASIC used this product.
It also began adoption by professional developers.
Around the same time a number of concepts were imported from C in order to let Pascal programmers use the C-based API of Microsoft Windows directly.
These extensions included null-terminated strings, pointer arithmetic, function pointers, an address-of operator and unsafe typecasts.
However, Borland later decided it wanted more elaborate object-oriented features, and started over in Delphi using the Object Pascal draft standard proposed by Apple as a basis.
(This Apple draft is still not a formal standard.) Borland also called this Object Pascal in the first Delphi versions, but changed the name to Delphi Programming Language in later versions.
The main additions compared to the older OOP extensions were a reference-based object model, virtual constructors and destructors, and properties.
There are several other compilers implementing this dialect, see Object Pascal.
Turbo Pascal, and other derivatives with units or module concepts are modular languages.
However, it does not provide a nested module concept or qualified import and export of specific symbols.
Super Pascal was a variant which added non-numeric labels, a return statement and expressions as names of types.
The universities of Zurich, Karlsruhe and Wuppertal have developed an EXtension for Scientific Computing (Pascal XSC) based on Oberon, which provides a free solution for programming numerical computations with controlled precision.
In 2005, at the Web 2.0 conference, Morfik Technology introduced a tool which allowed the development of Web applications entirely written in Morfik Pascal.
Morfik Pascal is a dialect of Object Pascal, very close to Delphi.
Language Constructs
Pascal, in its original form, is a purely procedural language and includes the traditional array of Algol-like control structures with reserved words such as if, then, else, while, for, and so on.
However, pascal also has many data structuring facilities and other abstractions which were not included in the original Algol60, like type definitions, records, pointers, enumerations, and sets.
Such constructs were in part inherited or inspired from Simula67, Algol68, and Niklaus Wirth's own AlgolW.
A syntactical comparison with C
Syntactically, Pascal is distinguished from languages in the C family by being much more Algol-like.
English keywords are retained where C uses punctuation symbols — pascal has and, or, and mod where C uses &&, ||, and % for example.
However, C is actually more Algol-like than Pascal regarding (simple) declarations, retaining the type-name variable-name syntax which Pascal abandoned to allow for (easily read) complex type expressions and a better perceived clarity in educational situations.
Another, more subtle, difference is the role of the semicolon.
In Pascal semicolons separate individual statements within a compound statement whereas, in C, they are syntactically part of the statement itself (transforming an expression into a statement).
This difference manifests itself primarily in two situations:
there can never be a semicolon directly before else in Pascal whereas it is mandatory in C (unless a block statement is used)
the last statement before an end is not required to be followed by a semicolon
Some programmers nevertheless put a semicolon on the last line before end, thereby formally inserting an empty statement.
This is discouraged by some educators, worried that it may confuse students' perception of the formal role of the semicolon.
Hello world
Pascal programs start with the program keyword, an optional list of external file descriptors and then a statement block is indicated with the begin and end keywords.
Semicolons separate statements, and the full stop ends the program (or unit).
Letter case is ignored in Pascal source.
Some compilers (Turbo Pascal among them) have made the program keyword optional.
Here is an example of the source code in use for a very simple program:
Code: program HelloWorld(output);
begin
writeln('Hello, World!')
end.
Data structures
Pascal's simple (atomic) types are real, integer, character, boolean and enumerations, a new type constructor introduced with Pascal:
Code: var
r: real;
i: integer;
c: char;
b: boolean;
e: (one, two, three, four, five);
Subranges of any ordinal type (any simple type except real) can be made:
Code: var
x: 1..10;
y: 'a'..'z';
z: two..four;
Types can be defined from other types using type declarations:
type
Code: x = integer;
y = x;
...
Further, complex types can be constructed from simple types:
type
Code: a = array [1..10] of integer;
b = record
a: integer;
b: char
end;
c = file of a;
As shown in the example above, Pascal files are sequences of components.
Every file has a buffer variable which is denoted by f^.
The procedures get (for reading) and put (for writing) move the buffer variable to the next element.
Read is introduced such that read(f, x) is the same as x:=f^;
Get(f);. Write is introduced such that write(f, x) is the same as f^ := x;
Put(f); The type text is predefined as file of char.
While the buffer variable could be used to inspect the next character that would be used (check for a digit before reading an integer), this concept leads to serious problems with interactive programs.
Pascal 6000 and VAX Pascal had incompatible solutions for this problem and most other implementations omit the get and put procedures.
In Jensen & Wirth Pascal, strings are represented as packed arrays of chars;
They therefore have fixed length and are usually space-padded.
Later dialects commonly add a string type where the length of the contents can vary up to a declared maximum length.
These are usually implemented by a length byte (limiting the maximum length to 255) and a fixed array of payload characters, and are therefore space-inefficient if the maximal length is seldom used in practice.
Pointers
Pascal supports the use of pointers:
Code: type
a = ^b;
b = record
a: integer;
b: char;
c: a
end;
var
pointer_to_b: a;
Here the variable pointer_to_b is a pointer to the data type b, a record.
To create a new record and assign the values 10 and A to the fields a and b in the record, the commands would be;
Code: new(pointer_to_b);
pointer_to_b^.a := 10;
pointer_to_b^.b := 'A';
pointer_to_b^.c := nil;
...
This could also be done using the with statement, as follows
Code: new(pointer_to_b);
with pointer_to_b^ do
begin
a := 10;
b := 'A';
c := nil
end;
...
Note that inside of the scope of the with statement, the compiler knows that a and b refer to the subfields of the record pointer pointer_to_b and not to the record b or the pointer type a.
Linked lists, stacks and queues can be created by including a pointer type field (c) in the record (see also nil and null (computer)).
Control structures
Pascal is a structured programming language, meaning that the flow of control is structured into standard statements, ideally without 'go to' commands.
Code: while a <>
B do writeln('Waiting');
if a >
B then
writeln('Condition met')
else
writeln('Condition false');
for i := 1 to 10 do writeln('Iteration: ', i:1);
repeat a := a + 1 until a = 10;
Procedures and functions
Pascal structures programs into procedures and functions.
Code: program mine(output);
var i : integer;
procedure print(var j: integer);
function next(k: integer): integer;
begin
next := k + 1
end;
begin
writeln('The total is: ', j);
j := next(j)
end;
begin
i := 1;
while i <= 10 do print(i)
end.
Procedures and functions can nest to any depth, and the 'program' construct is the logical outermost block.
Each procedure or function can have its own declarations of goto labels, constants, types, variables, and other procedures and functions, which must all be in that order.
This ordering requirement was originally intended to allow efficient single-pass compilation.
However, in most modern dialects the strict ordering requirement of declaration sections has been abandoned.
|
|
|
|
|
|
|
|